*** This bug is a duplicate of bug 703800 ***
https://bugs.launchpad.net/bugs/703800
@jneff yes the same for me, so the workaround doesn't work... because
the post-stop script try do delete the bridge but there is an error
"bridge lxcbr0 is still up; can't delete it" if all containers are not
*** This bug is a duplicate of bug 703800 ***
https://bugs.launchpad.net/bugs/703800
This happens because 'restart service' does not cause service's post-stop
to be executed. Only it's pre-stop is executed.
Note that if you want to stop the dnsmasq, you can work around this by
doing
stop lx
*** This bug is a duplicate of bug 703800 ***
https://bugs.launchpad.net/bugs/703800
In my tests on Ubuntu 14.04, the LXC dnsmasq process is restarted with:
$ sudo restart lxc-net
only when all guest containers are stopped. If one or more containers
are running, the dnsmasq process is left r
*** This bug is a duplicate of bug 703800 ***
https://bugs.launchpad.net/bugs/703800
Thanks for reporting this bug. This is actually a bug in upstart, not
lxc, reported as bug 703800. I'll mark it as a duplicate.
** This bug has been marked a duplicate of bug 703800
init: restart command
Scott
I can reproduce the restart issue, but using start/stop dnsmasq was
restarted:
ubuntu@server-15281:~$ ps axw | grep dnsm
5367 ?S 0:00 dnsmasq -u lxc-dnsmasq --strict-order
--bind-interfaces --pid-file=/var/run/lxc/dnsmasq.pid --conf-file=
--listen-address 10.0.3.1 --dhcp-ran
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1043588
Title:
sudo restart lxc-net does not kill/restart dnsmasq
To manage notifications about this bug go to:
https://bugs.launchpad.net
