Skip to content
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.

Docker failing to start some containers with memory limit using systemd for cgroup #1163

Closed
rawouter opened this issue Mar 10, 2016 · 1 comment

Comments

@rawouter
Copy link

As discussed with @philips, ccing @crawford

Reporting moby/moby#19406 bug with rapid container creation/deletion using systemd exec driver for cgroup. Some containers will fail starting with the following error if memory limit was set:

core@server ~ $ for i in {1..10}; do docker run -i --rm --memory=1g tianon/true; done
Error response from daemon: Cannot start container df673f834ef10b20ad8fb04b2ae70f2ec70a63fd653f3a451bd9d9d724b6fb57: [8] System error: write /sys/fs/cgroup/memory/system.slice/docker-df673f834ef10b20ad8fb04b2ae70f2ec70a63fd653f3a451bd9d9d724b6fb57.scope/memory.memsw.limit_in_bytes: invalid argument

@crawford
Copy link
Contributor

crawford commented Dec 2, 2016

We have since switched back to cgroupfs as the default for native.cgroupdriver. I'm going to go ahead and close this out.

@crawford crawford closed this as completed Dec 2, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants