[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)

[Serge Hallyn]

Thanks, Robert.

It looks like ssh is not being properly killed.  When we force it to die
with lxc-stop, it does not remove its /var/run/ files.  Then it fails to
start bc those already exist.

Until this is fixed, you can work around this by doing

  rm -rf /var/lib/lxc/<container-name>/rootfs/var/run
  mkdir !!:2

After this I'm able to restart the lucid container.  You can automate
this by changing your container's /etc/init/lxcmount to the one I'm
about to attach.  With that, I still need to kill the container by hand,
but then lxc-start works.

I'm tempted to wait to see if we can implement proper container
reboot/poweroff support at the lxc sprint next week, because the lxc-
monitor watching /var/run/utmp is an ugly hack anyway, and continually
finding ways to fix its breaks does not seem productive.

-- 
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/819621

Title:
  lucid container start failure after calling lxc-stop (fails across
  reboots)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions