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

Stéphane Graber stgraber at stgraber.org
Mon Apr 14 16:19:13 UTC 2014


Public bug reported:

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

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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:
  New

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



More information about the foundations-bugs mailing list