[Bug 1307595] Re: systemd-logind fails to start in unprivileged containers

[Launchpad Bug Tracker]

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 <stgraber at ubuntu.com>   Mon, 14 Apr 2014 12:20:33 -0400

** Changed in: systemd (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1307595

Title:
  systemd-logind fails to start in unprivileged containers

Status in “systemd” package in Ubuntu:
  Fix Released

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).

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