Jobs fail Randomly with Docker executor
Summary
Hello !
I use Gitlab CI runners in docker containers using gitlab/gitlab-runner:latest
image without problem since few month.
But since few days or week, I got issues with latest releases on multi-jobs Pipelines :
ERROR: Preparation failed: Error response from daemon: Conflict. The container name "/runner-94762e7a-project-65-concurrent-0-docker-0" is already in use by container "7b06028fb6eecc011d7c35a7355c854236e23db98e28746c02cd0be3150ce571". You have to remove (or rename) that container to be able to reuse that name.
or Persistent connexion closed
Steps to reproduce
Install latest Gitlab runner in Docker and launch multiple job for one Pipeline.
Actual behavior
1/4 jobs fails with latests releases.
Relevant logs and/or screenshots
Will be retried in 3s ... job=5820 project=65 runner=94762e7a
ERROR: Job failed (system failure): Error response from daemon: Conflict. The container name "/runner-94762e7a-project-65-concurrent-0-docker-0" is already in use by container "7b06028fb6eecc011d7c35a7355c854236e23db98e28746c02cd0be3150ce571". You have to remove (or rename) that container to be able to reuse that name. job=5820 project=65 runner=94762e7a
Environment description
Self Hosted Gitlab CE with Runner running on other VM (Debian w/ latest Docker version 17.06.0-ce/Overlay )
Used GitLab Runner version
# gitlab-runner -v
Version: 9.4.2