I can run containers manually from the command line on the instance (including the containers noted above) those containers start and behave normally.Īs a test, I updated Docker from 19.03 (our standard version) to 20.10.7 this did not change the behavior.īoth the GitLab runner and the Docker service are running as users with Administrator rights on the instance. The “add-host” in the error message suggests the “–add-host” option to the “docker run” command, which is supposed to “add a custom host-to-ip mapping” (per the Docker CLI documentation). This suggests that the problem is with Docker, rather than with the containers. gitlab-ci.yml file that references a Microsoft-built container ( /windows/servercore:1809) and simply tries to execute a PowerShell command.
#DOCKER IP ADDRESS YML WINDOWS#
OS Name: Microsoft Windows Server 2019 Datacenter The two IP addresses listed in the error message do not match the IP address of the instance or its default gateway.īased on the link in the error message, I verified that the OS version on the EC2 instance matches the OS version inside the container. Check Types of shells supported by GitLab Runner | GitLab for more information When I try to build a simple console hello-world program using the container, I get this message as soon as the build starts:ĮRROR: Job failed (system failure): prepare environment: Error response from daemon: invalid IP address in add-host: “172.27.84.100 172.27.82.245” (docker.go:651:0s). I have a Windows container image, based on /dotnet/framework/sdk:4.7.2-20191008-windowsservercore-ltsc2019, with some additional tools installed. I have two GitLab runners configured on this instance: a PowerShell runner (which runs jobs on the VM itself) and a Docker runner (that should run jobs using a container image specified in the. I have a Windows EC2 instance in AWS, with Docker installed.
0 kommentar(er)
