lxc fails to start inside vivid container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
init-system-helpers (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
lxc (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
upstart (Ubuntu) |
Fix Released
|
High
|
Unassigned |
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-
and exit 0. On a systemd host, /bin/running-
the profile loading script exits with error, failing the postinst.
/bin/running-
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/
Then move /bin/running-
Changed in init-system-helpers (Ubuntu): | |
status: | New → Triaged |
Changed in upstart (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in init-system-helpers (Ubuntu): | |
importance: | Undecided → High |
Changed in lxc (Ubuntu): | |
status: | Triaged → Fix Released |
This bug was fixed in the package upstart - 1.13.2-0ubuntu13
---------------
upstart (1.13.2-0ubuntu13) vivid; urgency=medium
* remove running- in-container - it is moved to init-system-helpers and
made to work also with systemd. (LP: #1442228)
-- Serge Hallyn <email address hidden> Thu, 09 Apr 2015 18:40:12 -0500