[lxc-users] Network and snapshots copied to another server

Steven Spencer sspencerwire at gmail.com
Thu Apr 4 16:00:56 UTC 2019


All,

We have a native LXD server (3.0.0) and I was curious about upgrading to
3.11 via snap. I installed an 18.04 LTS server and then installed lxd via
snap (3.11). I copied a few containers over that I could easily stop on the
native server. Installing 18.04 LTS server installs a native copy of LXD
(3.0.3) and so my first tests were just starting the container using the
native installed packages (no snap at this point). What I wasn't expecting
is that the static IP set on the CentOS 7 container did not follow it with
the snapshot, in fact it had the generic sysconfig ifcfg-eth0 settings as
if it was a new CentOS 7 container unconfigured:

DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
HOSTNAME=rocketchat
NM_CONTROLLED=no
TYPE=Ethernet
MTU=
DHCP_HOSTNAME=`hostname`

If I set the configuration to a static IP and upped the interface, it
worked as expected. I did a fair amount of searching on why the snapshot
does not contain the network information, but came up empty. Is this by
design and if so, is there a way to include the network settings as they
are on the production container with the snapshot?

My goal here was ultimately to test lxd.migrate with a few containers
copied over (snapshots) and that does seem to work, sans the network
information. (yes, the lxd.migrate is a totally separate issue, just
letting you know what my goal was when I started this.)

Thanks,
Steven G. Spencer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20190404/3f0b4004/attachment.html>


More information about the lxc-users mailing list