touch-packages team mailing list archive

[Launchpad Bug Tracker <1442228@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package init-system-helpers - 1.22ubuntu10

---------------
init-system-helpers (1.22ubuntu10) vivid; urgency=medium

  * Move /bin/running-in-container from upstart and update it so that
    systemd-based vivid hosts can use it.  (LP: #1442228)
 -- Serge Hallyn <serge.hallyn@xxxxxxxxxx>   Thu, 09 Apr 2015 18:40:41 -0500

** Changed in: init-system-helpers (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1442228

Title:
  lxc fails to start inside vivid container

Status in init-system-helpers package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Triaged
Status in upstart package in Ubuntu:
  Fix Released

Bug description:
  When installing lxc, the lxc.postinst tries to install apparmor profiles.
  Inside a vivid container on an upstart-based host, the profile loading
  script will test /bin//running-in-container and see that it is in a container
  and exit 0.  On a systemd host, /bin/running-in-container doesn't work, so
  the profile loading script exits with error, failing the postinst.

  /bin/running-in-container needs to be generalized to work with
  systemd.

  Unlike upstart, systemd leaves its environment showing in /proc/1/environ,
  so we can in fact simply check for "grep -q container=lxc /proc/1/environ",
  which we couldn't do with upstart.  However, to keep things more similar
  between upstart and systemd, and to handle all cases, it would probably be
  best to have a systemd unit starting at boot which does the same thing as
  the /etc/init/container-detect.conf does.

  Then move /bin/running-in-container from upstart into init-system-
  helpers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1442228/+subscriptions