Description of problem: Not able to write to memory.memsw.limit_in_bytes. Example: -bash-4.3# rpm -q docker-io systemd docker-io-1.4.1-5.fc21.x86_64 systemd-216-17.fc21.x86_64 -bash-4.3# docker run --rm --memory 500M busybox echo "I'm Alive" FATA[0003] Error response from daemon: Cannot start container d79629bfddc7833497b612e2b6d4cc2542ce9a8c2253d39ace4434bbd385185b: write /sys/fs/cgroup/memory/system.slice/docker-d79629bfddc7833497b612e2b6d4cc2542ce9a8c2253d39ace4434bbd385185b.scope/memory.memsw.limit_in_bytes: invalid argument This has been fixed by [1] and is somewhat documented in [2]. A full reproducer for F21 atomic host can be found at [3]. [1] - http://cgit.freedesktop.org/systemd/systemd/commit/?id=a3bd89ea99 [2] - https://github.com/docker/docker/issues/10280 [3] - http://dustymabe.com/2015/01/31/crisis-averted-im-using-atomic-host/
*** Bug 1187882 has been marked as a duplicate of this bug. ***
systemd-216-20.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/systemd-216-20.fc21
Package systemd-216-20.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-216-20.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-1793/systemd-216-20.fc21 then log in and leave karma (feedback).
systemd-216-20.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
is this being backported to the systemd that ships in EL7 as well? we're definitely impacted on fully updated CentOS 7 running 208-11.el7_0.6.
Dunno. Ask in the CentOS bugtracker maybe.