How to start a container if Docker says there is no free space but df shows there is?

Question

Docker

Good afternoon!
Faced for the first time with a strange problem for me.
There is an image, on the basis of it 2 containers are spinning. The location paths are standard, have not changed.
Everything was assembled and started without errors. It took to start 1 more instance of the container:

docker run -d -p 30024:22 -v <path...>:<path...> -e "USER=user" -e "PASS=pass" --name user -h user -it techportal

but when run:

docker: Error response from daemon: write /var/run/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/7dcca35874e0689976ac368093927d83e6ff803ed889d4fc47cb26d380bef019/config.json: no space left on device: unknown.

df-h

df -h
Filesystem           Size  Used Avail Use% Mounted on
/dev/mapper/cl-root   79G   38G   42G  48% /
devtmpfs             884M     0  884M   0% /dev
tmpfs                895M     0  895M   0% /dev/shm
tmpfs                895M  895M     0 100% /run
tmpfs                895M     0  895M   0% /sys/fs/cgroup
/dev/xvda1           984M  121M  797M  14% /boot
tmpfs                179M     0  179M   0% /run/user/600
tmpfs                179M     0  179M   0% /run/user/1001
tmpfs                179M     0  179M   0% /run/user/0
tmpfs                179M     0  179M   0% /run/user/1000
overlay               79G   38G   42G  48% /var/lib/docker/overlay2/d0a0019739e0ac612231d29203d91f07548e89492105afb2d60eb889d81df3ff/merged
shm                   64M     0   64M   0% /var/lib/docker/containers/240484373ad52c4e7db7cfea9302a37bb5c4b0e855ea7f02ee16750751fbe33a/mounts/shm
overlay               79G   38G   42G  48% /var/lib/docker/overlay2/70aec8465d1f3bde1ec875bd71e4a7ba884e3d008cd9afaf5279430c770efe96/merged
shm                   64M     0   64M   0% /var/lib/docker/containers/8b17bb767a416113eb71b666a7415d7a255f6b00a5665062e7be7d49302951f0/mounts/shm

Actually, the question is: why, when there is a place, does he say otherwise? Or I don't understand something, please explain.

Answer 1

The issue was resolved by cleaning the /run directory, because the problem was in the insufficient amount of space in it.