Am 05.07.2018 um 04:14 schrieb Ryutaroh Matsumoto: > Package: systemd > Version: 239-4 > Severity: normal > > Dear Maintainer, > > I can impose CGroup V2 memory limitation by > systemd-run --user -t -p "MemoryHigh=1G" /bin/bash > > Within the bash, I see > > $ cat > /sys/fs/cgroup/user.slice/user-1005.slice/user\@1005.service/run-u0.service/memory.high > > 1073741824 > > and the memory limitation seems working. It has been convenient > for preventing memory-eating applications from eating > all the physical memory. > > I verified the above behavior in Ubuntu 18.04 LTS running > in systemd-nspawn. Its systemd package version is > 237-3ubuntu10. Host Linux is also Ubuntu 18.04 LTS. > > When I do the same in Debian Unstable (in a container), > "memory.high" does not appear and the memory limitation > does not seem working. The configuration of Debian Unstable > is almost the same as Ubuntu 18.04 running in a container. > Specifically, > > * dbus-session-user package is chosen to enable systemd-run --user. > Alternative choice may be dbus-x11. > > * /etc/systemd/system/[email protected]/delegate.conf has the following > [Service] > Delegate=memory pids cpu io > > * Host Linux has the following kernel command line to let systemd > use CGroup V2 (Otherwise MemoryHigh is unusable). > systemd.unified_cgroup_hierarchy=1 >
Thanks for your bug report. Can you please raise this issue upstream at https://github.com/systemd/systemd/issues and report back with the bug number. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
