On Wed, Sep 27, 2017 at 09:48:39PM +0900, Tomasz Chmielewski wrote: > # lxc exec some-container /bin/bash > The configuration file contains legacy configuration keys. > Please update your configuration file! > > > > Is there a way to tell find out which ones are legacy without pasting the > whole config on the mailing list? > > > Tomasz Chmielewski > https://lxadm.com
In most cases, it's just that the container was started on LXC 2.0.x, so just restarting it will have LXD generate a new LXC 2.1 config for it, getting you rid of the warning. If that warning remains, then it means you're using a "raw.lxc" config in your container or one of its profile and that this key is the one which contains a now legacy config key. Details on key changes can be found here: https://discuss.linuxcontainers.org/t/lxc-2-1-has-been-released/487 The tl&dr; is that for 99% of LXD users, all you need to do is restart your running containers so that they get switched to the new config format, no config change required. The remaining 1% is where you're using raw.lxc which then needs manual updating to get rid of the warning. -- Stéphane Graber Ubuntu developer http://www.ubuntu.com
signature.asc
Description: PGP signature
_______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
