Output of docker version:
Client:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Tue Apr 26 23:20:46 2016
OS/Arch: linux/amd64
Server:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Tue Apr 26 23:20:46 2016
OS/Arch: linux/amd64
Output of docker info:
# docker info
Containers: 555
Running: 197
Paused: 0
Stopped: 358
Images: 109
Server Version: 1.11.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 1242
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: null host bridge
Kernel Version: 3.16.0-4-amd64
Operating System: Debian GNU/Linux 7 (wheezy)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.324 GiB
Name: e2e-test-dawnchen-minion-18ah
ID: UZMP:J3YN:4AHS:RHBP:SSQH:EKFD:PRQR:HGFN:DRPL:JWZR:RJZL:TEQR
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
WARNING: No kernel memory limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
Additional environment details (AWS, VirtualBox, physical, etc.):
Just a standard Kubernetes node with docker 1.11.1
Steps to reproduce the issue:
I just simply run the command and quickly hit the cap (~200)
for i in {1..500}; do echo $i; docker run -d --name container$i gcr.io/google_containers/pause:2.0; done
The error message:
1
410d715441504b1e93d77cdec531b338631fcafd637215376df2e8e65d27484e
...
ec5255dc7d1b69624f9f3cc4687708286cc7aefb6b3cd32024d0e41701678337
177
ab99e85ac7b67204ba0c3ff0214dd319bd79fcb06285925c936614a43aa34416
178
dfddfc1ac3bc43625616677385ad68137295af69bfd7274691448476f4cbe675
179
741e2d5708b95469afa65967fafaaf04175ae792eaf6fb3284a5209dcfd71a1c
180
90242513e32aa465ce8fe0df5ab79a0bcd3af4cb32723470f589bff943748c30
181
d77c7e9f06724b1aee0e98f587dba04212a7449723786c5ea7a5bdf623896a38
182
e5631849be2cbe9ced9d463cd00267f8185a9df776f40e9015825a899f755028
docker: Error response from daemon: rpc error: code = 2 desc = "oci runtime error: could not synchronise with container process: could not create session key: disk quota exceeded".
183
e542d7ed3cdfe61add072d47abc23f41f2386ea4df82491415c76cb4ed168326
docker: Error response from daemon: rpc error: code = 2 desc = "oci runtime error: could not synchronise with container process: could not create session key: disk quota exceeded".
184
cc6034b216e191242dfa825d37c5b514ff5133e26dc00c3fa1ea8c6b9fbb5871
docker: Error response from daemon: rpc error: code = 2 desc = "oci runtime error: could not synchronise with container process: could not create session key: disk quota exceeded".
185
53c0b3d65d9f1b6d87cd385cf7d90d79983b518dd4f5d57779e615e9a23d4220
docker: Error response from daemon: rpc error: code = 2 desc = "oci runtime error: could not synchronise with container process: could not create session key: disk quota exceeded".
186
8f74f50ea15dee4dd286189de828ec2333644e1552d5436976ad0e458da5604d
docker: Error response from daemon: rpc error: code = 2 desc = "oci runtime error: could not synchronise with container process: could not create session key: disk quota exceeded".
187
a7ed9ce29299e70414390490b4f8c103b284d12ef7e85d20efa182211b356a1f
docker: Error response from daemon: rpc error: code = 2 desc = "oci runtime error: could not synchronise with container process: could not create session key: disk quota exceeded".
...
500
237e185ab8b5b0774b09c058bed74f0331da8a1c999ec614bac69ad98106bf77
docker: Error response from daemon: rpc error: code = 2 desc = "oci runtime error: could not synchronise with container process: could not create session key: disk quota exceeded".
I believe we are hitting at this issue: opencontainers/runc#726, but an attempt solution (opencontainers/runc#727) was closed and the suggestion is the issue should be handled at the higher layer, which I believe it should be docker engine here.
Output of docker version:
Output of docker info:
Additional environment details (AWS, VirtualBox, physical, etc.):
Just a standard Kubernetes node with docker 1.11.1
Steps to reproduce the issue:
I just simply run the command and quickly hit the cap (~200)
The error message:
I believe we are hitting at this issue: opencontainers/runc#726, but an attempt solution (opencontainers/runc#727) was closed and the suggestion is the issue should be handled at the higher layer, which I believe it should be docker engine here.