[Bug 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)
Ubuntu Foundations Team Bug Bot
1830746 at bugs.launchpad.net
Tue May 28 16:22:29 UTC 2019
The attachment "fix-memlock-bump.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]
** Tags added: patch
--
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/1830746
Title:
memlock setting in systemd (pid 1) too low for containers (bionic)
Status in systemd package in Ubuntu:
New
Bug description:
See also https://discuss.linuxcontainers.org/t/limits-kernel-memlock-
cannot-exceed-16777216/4856/5
In containers, the limits.kernel.memlock cannot exceed 16777216 when
the container is bionic. The memlock setting is set to 16M in systemd
and cannot be bumped up in an unprivileged container.
This is fixed in upstream systemd.
Container ubuntu version:
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
systemd package version: 237-3ubuntu10.21
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746/+subscriptions
More information about the foundations-bugs
mailing list