** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458173
Title:
Vivid + LXC autostart not working
To manage notifications about
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458173
Title:
Vivid + LXC autostart not working
To manage notifications about this
The race between lxc-net and lxc-containers should be fixed with a patch
sent upstream. To apply the fix locally, add "lxc-net.serve " to the
After= line in /lib/systemd/system/lxc.service
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: lxc (Ubuntu)
Status: New
Could you try editing /lib/systemd/system/lxc-net.service to change
ExecStart=/usr/libexec/lxc/lxc-net start
to
ExecPreStart=/usr/libexec/lxc/lxc-net start
and see whether that reliably fixes it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I would be curious to see whether switching from systemd back to upstart
fixes this.
/lib/systemd/system/lxc.service declares a 'Wants" on
/lib/systemd/system/lxc-net.service which should create the bridge, so
I'm really curious as to what's going on.
--
You received this bug notification becaus
Workaround is to run a script in /etc/rc.local that waits for the bridge
adapter to come up + then runs lxc-autostart.
This script can be run in background, for example...
/etc/rc.local snippet...
# LXC autostart boot hack
# Track https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458173 for
d
lxc-autostart after boot works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458173
Title:
Vivid + LXC autostart not working
To manage notifications about this bug go to:
https://bugs.launchpad.n
