<thumper> hallyn: has the autostart behaviour for lxc changed in trusty? <hallyn> thumper: yes, stgraber's new autostart setup may be in now. certainly in the ppa <stgraber> hallyn: yep, it landed with beta2 last week <thumper> hallyn: hmm... managed to break juju's behaviour <thumper> hallyn: can you explain the change? <hallyn> juju uses autostart? <stgraber> thumper: yes, autostart settings are now upstream and use the container's config instead <thumper> hallyn: yep, <stgraber> thumper: I believe I already told someone this morning wrt juju <stgraber> thumper: use "lxc.start.auto = 1" in the container config <thumper> stgraber: don't expect us to talk to each other :-) <hallyn> stgraber: remind me, is there any attempt at auto-conversion for /etc/lxc/auto/ users? <stgraber> hallyn: yes, there's migration code, but it won't do them much good for new juju containers <hallyn> heh yah <stgraber> any container on the system at the time of the upgrade to beta2 should have been automatically converted (symlink removed, /etc/lxc/auto removed and lxc.start.auto = 1 added to the container config) <thumper> stgraber: is this lxc going into the cloud archive? <thumper> stgraber: for precise? <thumper> is there a way we can work out if this is supported? <stgraber> thumper: maybe hallyn knows, I usually ignore the existence of that external archive entirely -*- thumper nods <stgraber> thumper: rule of thumb would be, if /etc/lxc/auto exists, use it, if not, use lxc.start.auto = 1 <thumper> stgraber: that makes sense... <thumper> should be able to handle that pretty easily
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1271941 Title: lxc container creation fails on trusty host service units To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
