I have some problems recently with Docker filling all the space in my /run tmpfs. It wasn’t the case before. I increased the RAM memory on a first server but that’s not a permanent solution.
When I start a container, i have this message :
ERROR: for matomo-app Cannot start service matomo-app: write /var/run/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/7641c3a23eb4a4bb822a9fafcd731c6c43b87503337a059591c17cb6e1e4d5bc/config.json: no space left on device: unknown
Okay, so I do a
df -h and my
/run is full :
tmpfs 496M 447M 0M 100% /run
And then I discovered that all the space is filled up by “pid” files located in
/run/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/CONTAINER_ID where CONTAINER_ID is ID of my containers.
Interesting fact, each folder weighs 50M. In each folder, I have 12653 PID files, each one weighs 4,0K, so it’s approximately 50M.
Don’t know if it’s related but I’m using Docker on a VMWare ESXi (Ubuntu 16.04).
It’s weird that Docker has to create so many PID files, isn’t it ?
Thank you for your time