Re: [lxc-users] "The configuration file contains legacy configuration keys" - which ones?

On Wed, Sep 27, 2017 at 10:07:13PM +0900, Tomasz Chmielewski wrote: > On 2017-09-27 22:03, Stéphane Graber wrote: > > 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. > > >

Re: [lxc-users] "The configuration file contains legacy configuration keys" - which ones?

On 2017-09-27 22:03, Stéphane Graber wrote: 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

Re: [lxc-users] "The configuration file contains legacy configuration keys" - which ones?

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 >

Re: [lxc-users] "The configuration file contains legacy configuration keys" - which ones?

I add myself to the question. On Wed, Sep 27, 2017 at 8:48 AM, 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

[lxc-users] "The configuration file contains legacy configuration keys" - which ones?

# 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

Re: [lxc-users] Steam BPM X360 controller detection inside container

Thanks for your reply Stéphane. Using udevadm monitor I observed KERNEL events propagating inside the container when the controller was attached (I imagined this was because the container is running in privileged mode), so I thought there might be a way to manually create a uevent inside the

Re: [lxc-users] containers and lxdbr0 bridge lost ip after upgrade on 2.18

Yes it's a dnsmasq version parsing issue Thanks for the fix 26 septembre 2017 15:07 "Stéphane Graber" a écrit: > On Fri, Sep 22, 2017 at 02:29:15PM +, Laurent Ducos wrote: > >> Hello >> After xenial ubuntu upgrade lxd switch to 2.18 >> i reboot and no ip for lxdbr0 and