[Bug 1830746] Re: memlock setting in systemd (pid 1) too low for containers (bionic)
Dimitri John Ledkov
launchpad at surgut.co.uk
Wed May 29 18:12:58 UTC 2019
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Eoan)
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/1830746
Title:
memlock setting in systemd (pid 1) too low for containers (bionic)
Status in systemd package in Ubuntu:
New
Status in systemd source package in Bionic:
New
Status in systemd source package in Cosmic:
New
Status in systemd source package in Disco:
New
Status in systemd source package in Eoan:
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