Tomasz Chmielewski writes:
> In other words - how to best achieve:
>
> - tar a selected container
>
> - copy it via SSH somewhere
>
> - restore at some later point in time somewhere else, on a different,
> unrelated LXD server
Probably it's not the best way to do it, but you
Tomasz Chmielewski writes:
> While I can imagine setting up many OpenVPN tunnels between all LXD
> servers (LXD1-LXD2, LXD1-LXD3, LXD2-LXD3) and constantly adjusting the
> routes as containers are stopped/started/migrated, it's a bit of a
> management nightmare. And even more so
"Fajar A. Nugraha" writes:
> I'm confused.
>
> How did you managed to get it build, when the source from
> http://packages.ubuntu.com/xenial-updates/lxd has
>
> Build-Depends: debhelper (>= 9),
...
>golang-petname-dev,
...
> and
Paul Dino Jones writes:
> So, i see lxc 2.0 has made it's way into Stretch and Jessie backports,
> but I don't see any activity on lxd. Is this going to happen in time
> for the Stretch freeze?
I've packaged LXD for Jessie (Devuan's, but the same applied to Debian),
Micky Del Favero <mi...@mesina.net> writes:
> In the last few days I've managed to setup lxd on Devuan Jessie
> (http://devuan.org/) but the same applied to Debian Jessie, I think it
> may be helpful to other and so I'll explain what I've done.
During last year some things cha
Micky Del Favero <mi...@mesina.net> writes:
> Probably I'm doing something wrong, but I'm not able to identify what,
> with LXD 0.24 I've no problem at all (even if my hack, see next mail).
Yesterday I investigate a bit and solve the issue, it's sufficient to
set:
auto_set_activat
Hello everybody!
LXD has hardcoded ext4 as the filesystem to be used when LVM storage
backend is choosed, I don't like very much ext* filesystems and prefer
xfs over them so I've done a little hack to be able to use it with LXD
0.24 and LVM storage, attached there's the patch agaist LXD 0.24 that
Merry Christmas to everybody! (even if I'm a bit late...)
I'm not able to use LXD 0.25 or the version cloned from github.com with
LVM storage backend, when I try to launch a container I've get:
micky@lina:~$ lxc remote add images images.linuxcontainers.org
Generating a client certificate.