Christian can confirm for traditional LXC/liblxc but there I would
expect that we keep the configuration as it is, tear down the
namespace and spawn init again in an identically configured set of
LXD is a bit different because we want to allow for reconfiguring on
reboots and we have a bunch of things that can happen on the LXD side
too, like snapshots on reboot, complex network/storage setups, ..
So in the LXD case, we configure liblxc to completely kill the
container during a reboot, then notify LXD about it (through a
post-stop hook) and then LXD will start the container again as if it
was freshly started.
> You received this message because you are subscribed to the Google Groups "lxc-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to lxc-users+...@lists.linuxcontainers.org
> To view this discussion on the web visit https://groups.google.com/a/lists.linuxcontainers.org/d/msgid/lxc-users/4c0b29c0-ca26-39eb-8e49-703e60ea30f2%40aixigo.com