Closed djeanprost closed 6 months ago
What's your runner's host OS? (see #466 and #467, one of which this is probably a duplicate of, and #468 which is where we're trying to workshop fixes)
For us, the last image of dind caused no issues on runners that are up-to-date. But we also had the network issue when using docker:dind
as a service in GitLab CI, on an older server.
Output of docker --version
on the host of the GitLab runner:
Docker version 20.10.24+dfsg1, build 297e128
: no issueDocker version 20.10.7, build f0df350
: no networkPinning the image to docker:20.10.7-dind
fixed the network issue.
Yeah, that matches one of #466 and #467, so I'm going to close this in favor of those two :innocent: :heart:
Hello,
I've referenced version 24 of docker image and dind image when executing a pipeline in gitlab runner. Suddenly, I started to get what I would call network issues. My pipeline started to run 24.0.7 after 24.0.6 When I run in 24.0.7, I get network issues I cannot explain. Reverting to 24.0.6 does the job. I cannot explain what changed between those two versions, but something related to network changed.
What fails is that DNS doesn't work anymore
Test KO with 24.0.7 :
Test OK with 24.0.6