Gitlab runner error with docker on windows 10

Summary

We use Gitlab runner with docker on windows 10 and we have a docker error : Cannot create a file when that file already exists.

Steps to reproduce

• Install last version of Docker on Windows 10 pro.

• run a gitlab-ci-multi-runner on this computer (runner in docker mode)

• Create a .gitlab-ci.yml who use this runner

Actual behavior

Gitlab-ci output :

Running with gitlab-ci-multi-runner 9.1.0~beta.29.g85e9d98 (85e9d98) on BOD638 (0feb1ab2)

Using Docker executor with image prepack_vs2012 ...

ERROR: Failed to create container volume for /builds/vdupuis Failed to import image: Error response from daemon: re-exec error: exit status 1: output: link \?\C:\ProgramData\Docker\windowsfilter\27c28daf948d6ea7ffe33f23c603955207b5851cc61f8f353c50c892f6e2db97\usr\share\terminfo\2\2621 \?\C:\ProgramData\Docker\windowsfilter\27c28daf948d6ea7ffe33f23c603955207b5851cc61f8f353c50c892f6e2db97\usr\share\terminfo\2\2621a: Cannot create a file when that file already exists.

ERROR: Preparation failed: Failed to import image: Error response from daemon: re-exec error: exit status 1: output: link \?\C:\ProgramData\Docker\windowsfilter\27c28daf948d6ea7ffe33f23c603955207b5851cc61f8f353c50c892f6e2db97\usr\share\terminfo\2\2621 \?\C:\ProgramData\Docker\windowsfilter\27c28daf948d6ea7ffe33f23c603955207b5851cc61f8f353c50c892f6e2db97\usr\share\terminfo\2\2621a: Cannot create a file when that file already exists.

Will be retried in 3s ...

Used GitLab Runner version

gitlab-ci-multi-runner 9.1.0~beta.29.g85e9d98 (85e9d98)

mentioned in issue #2176

Here a picture of our process :

1. Push a branch on gitlab

2. gitlab start a gitlab-ci-multi-runner (in docker mode) on a Windows 10 pro

3. gitlab-ci-multi-runner start a docker image

4. In our case : a windows server docker image

5. The build is run

• On our case we have the issue at the step 3)
• The docker image works fine if we start it directly with docker
• Our process works fine if we use a linux docker image at the step 3) and 4)

I am available if you need additional informations. Thanks and regards

mentioned in issue #1729

I have exactly the same issue when using Windows Server 2016 with Docker EE.

If you run gitlab-runner --debug run on your Windows machine you might see more details. What i found out so far is that the bash-detection raises another issue, which we should discuss with @ayufan, as he wrote the bashDetectShell.

Since docker 1.12 there's a new Dockerfile command SHELL which might be interesting if we could use it, because the shell we have to instantiate in Windows Containers is powershell.

I believe that we need someone with a lot of Windows experience to have a full look at how our Windows integration does look. As I see it, we have number of problems there :(

i'll give it a try to modify bashDetectShell and see what pops up next ;-)

Sound like a good idea. I'm available if you have some runner to test. Thanks a lot.

Hello, can you give me some more info on steps 1 and 2 you're using ? I think this could be an ACL issue

Hi,

We use gitlab 9.0.5. We push a branch an a gitlab runner is started. With use gitlab runner 9.1.0~beta.29. This runner is started in a Windows 10 pro environment.

Could you give me your .gitlab-ci.yml file in order to review the process ? It seems to be linked to docker

Yeah, the Docker Executor does not work for Windows for multiple reasons. There is some additional information in #1775.

I didn't find anything about antivirus, did you try to exclude gitlab-ci-multi-runner-windows-amd64.exe from the real time analysis or the firewall (as docker uses the network, firewall embedded in antivirus thinks it's a threat) ! That was my major issue using docker on Windows to access shared files and the errors wasn't very verbose... Give it a try (I don't have setup a project to reproduice this specific error yet - but i will when time will be slower)