Xenial container on Xenial host no longer runs systemd and can't get an IP address

[Christopher Townsend]

I have a Xenial host with a Xenial LXC and as of today's updates, the container no longer gets an IP address and systemd does not appear to have run.

This same exact container worked fine last Friday, only packages on my host changed.

Also, I'm not sure if other host/LXC distro combinations are affected.

[Christopher Townsend (townsend)]

I've attached the list of packages that were updated when this issue started to occur.

[kevin gunn (kgunn72)]

fwiw, i just created an Ubuntu Core of xenial running it as a vm, and i am seeing the same thing

[Serge Hallyn (serge-hallyn)]

Can you show exactly how you create+start the container? (Are you using lxd?)

[Serge Hallyn (serge-hallyn)]

never mind, i can trivially reproduce it here - thanks

[Launchpad Janitor (janitor)]

This bug was fixed in the package lxcfs - 0.12-0ubuntu5

---------------
lxcfs (0.12-0ubuntu5) xenial; urgency=medium

  * prune init slice in caller_may_see_dir (LP: #1519079)

 -- Serge Hallyn <email address hidden> Mon, 23 Nov 2015 14:42:53 -0600

[Christopher Townsend (townsend)]

Thanks! This is indeed fixed now on Xenial.

[Stéphane Graber (stgraber)]

Hello Christopher, or anyone else affected,

Accepted lxcfs into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxcfs/0.10-0ubuntu2.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Ubuntu Foundations Team Bug Bot (crichton)]

The fix for this bug has been awaiting testing feedback in the -proposed repository for wily for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository.

[Christopher Townsend (townsend)]

Sorry, I don't have a Wily machine to verify the SRU on. Hopefully someone can verify before the SRU gets removed.

[Launchpad Janitor (janitor)]

This bug was fixed in the package lxcfs - 0.10-0ubuntu2.3

---------------
lxcfs (0.10-0ubuntu2.3) wily-proposed; urgency=medium

  * On upgrade, ask admin to reboot rather than restarting (LP: #1518117)
  * debian/tests/exercise: Make test_confinement.sh executable
  * Prune init slice in caller_may_see_dir() check. (LP: #1519079)

lxcfs (0.10-0ubuntu2.2) wily-proposed; urgency=medium

  * Fix container reboot with systemd >= 226. (LP: #1514690)

 -- Serge Hallyn <email address hidden> Wed, 25 Nov 2015 12:20:53 -0600

[Martin Pitt (pitti)]

The verification of the Stable Release Update for lxcfs has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.