When using docker, the worker sometimes does not run properly after several restarts, because dockerd fail to start properly.
The issue is random and only arise after multiple restart of the fame docker instances.
Steps to Reproduce
Execute docker-compose up --build, wait few minutes, then CTRL+C
Repeat the process multiple times. The error should happen after a while.
Expected behavior
dockerd should be able to always run correctly inside the worker container.
Debug
The root cause seems to be related to how docker stops the containers: When the worker is being shut down, dockerd sometimes doesn't have the time to stop properly inside the worker.
This causes leftover .sock & .pid files to remain on the worker's disk. dockerd will refuse to run on next restart because of these leftover files.
Description
When using docker, the worker sometimes does not run properly after several restarts, because
dockerdfail to start properly.The issue is random and only arise after multiple restart of the fame docker instances.
Steps to Reproduce
docker-compose up --build, wait few minutes, then CTRL+CExpected behavior
dockerdshould be able to always run correctly inside the worker container.Debug
The root cause seems to be related to how docker stops the containers: When the worker is being shut down,
dockerdsometimes doesn't have the time to stop properly inside the worker. This causes leftover.sock&.pidfiles to remain on the worker's disk.dockerdwill refuse to run on next restart because of these leftover files.