systemd-logind fails to start in unprivileged containers
Bug #1307595 reported by
Stéphane Graber
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Because of systemd-logind using the "limit" upstart stanza, it fails to start in unprivileged containers where the ulimit is lower than the requested one.
The proposed fix is to call ulimit from the job itself instead and ignore the failure (it'll get logged though in case this ends up causing some issues).
Related branches
To post a comment you must log in.
This bug was fixed in the package systemd - 204-5ubuntu20
---------------
systemd (204-5ubuntu20) trusty; urgency=medium
* systemd- logind. conf: Don't use the limit stanza which fails the
whole job when failing to set the ulimit. Instead call ulimit itself
from the job and ignore its return code. This allow systemd-logind to
start in unprivileged LXC containers. (LP: #1307595)
-- Stephane Graber <email address hidden> Mon, 14 Apr 2014 12:20:33 -0400