GitLab CI Runner: docker container already in use
I've seen this failure for a couple of jobs now, for example: https://gitlab.freedesktop.org/robertfoss/virglrenderer/-/jobs/71730
From what I understand, container appears to be stuck in a zombie state and needs to be restored.
Running with gitlab-runner 11.5.0 (3afdaba6)
on fdo-gitlab-gce-runner3 81280d8f
Using Docker executor with image docker:latest ...
Starting service docker:dind ...
Pulling docker image docker:dind ...
Using docker image sha256:dfd9350d475b431e4b9b037fe31f4f0df70d597688776f3b13e273a8c2ecc680 for docker:dind ...
WARNING: Can't disconnect possibly zombie container runner-81280d8f-project-1722-concurrent-0-docker-0 from network bridge -> Error response from daemon: Container 760789a5ebc5306b1c4f620f4d80b613a3c36cb83e3077d40eacf09da8c9fac4 is marked for removal and cannot be connected or disconnected to the network (executor_docker.go:1081:0s)
ERROR: Preparation failed: Error response from daemon: Conflict. The container name "/runner-81280d8f-project-1722-concurrent-0-docker-0" is already in use by container "760789a5ebc5306b1c4f620f4d80b613a3c36cb83e3077d40eacf09da8c9fac4". You have to remove (or rename) that container to be able to reuse that name. (executor_docker.go:706:0s)
Will be retried in 3s ...
Using Docker executor with image docker:latest ...
Starting service docker:dind ...
Pulling docker image docker:dind ...
Using docker image sha256:dfd9350d475b431e4b9b037fe31f4f0df70d597688776f3b13e273a8c2ecc680 for docker:dind ...
WARNING: Can't disconnect possibly zombie container runner-81280d8f-project-1722-concurrent-0-docker-0 from network bridge -> Error response from daemon: Container 760789a5ebc5306b1c4f620f4d80b613a3c36cb83e3077d40eacf09da8c9fac4 is marked for removal and cannot be connected or disconnected to the network (executor_docker.go:1081:0s)
ERROR: Preparation failed: Error response from daemon: Conflict. The container name "/runner-81280d8f-project-1722-concurrent-0-docker-0" is already in use by container "760789a5ebc5306b1c4f620f4d80b613a3c36cb83e3077d40eacf09da8c9fac4". You have to remove (or rename) that container to be able to reuse that name. (executor_docker.go:706:0s)
Will be retried in 3s ...
Using Docker executor with image docker:latest ...
Starting service docker:dind ...
Pulling docker image docker:dind ...
Using docker image sha256:dfd9350d475b431e4b9b037fe31f4f0df70d597688776f3b13e273a8c2ecc680 for docker:dind ...
WARNING: Can't disconnect possibly zombie container runner-81280d8f-project-1722-concurrent-0-docker-0 from network bridge -> Error response from daemon: Container 760789a5ebc5306b1c4f620f4d80b613a3c36cb83e3077d40eacf09da8c9fac4 is marked for removal and cannot be connected or disconnected to the network (executor_docker.go:1081:0s)
ERROR: Preparation failed: Error response from daemon: Conflict. The container name "/runner-81280d8f-project-1722-concurrent-0-docker-0" is already in use by container "760789a5ebc5306b1c4f620f4d80b613a3c36cb83e3077d40eacf09da8c9fac4". You have to remove (or rename) that container to be able to reuse that name. (executor_docker.go:706:0s)
Will be retried in 3s ...
ERROR: Job failed (system failure): Error response from daemon: Conflict. The container name "/runner-81280d8f-project-1722-concurrent-0-docker-0" is already in use by container "760789a5ebc5306b1c4f620f4d80b613a3c36cb83e3077d40eacf09da8c9fac4". You have to remove (or rename) that container to be able to reuse that name. (executor_docker.go:706:0s)