I’ve been using Gitlab CI with Gitlab.com for some time and I never had any issues with shared runners. Unfortunately, we’re seeing some failures in testing Docker images with Goss.
Goss Test Docker Image:
stage: test
script:
- apk add bash curl --no-cache
- curl -fsSL https://goss.rocks/install | sh
- docker pull $CI_REGISTRY_IMAGE/test:$CI_COMMIT_REF_SLUG
- dgoss run -ti --entrypoint=sh $CI_REGISTRY_IMAGE/test:$CI_COMMIT_REF_SLUG
So, when dgoss runs it can’t start the container. It used to work until about a week ago, not change has been made. Does anyone had similar issue?
It may be related to some warnings I’m seeing with shared runners:
Running with gitlab-runner 12.5.0-rc1 (b295d93b)
on docker-auto-scale fa6cab46
Using Docker executor with image docker:latest ...
Starting service docker:dind ...
Pulling docker image docker:dind ...
Using docker image sha256:eaed9efc02d231a28b0f7725551a71459a7763e83bcda5464db66ec4684a1639 for docker:dind ...
Waiting for services to be up and running...
*** WARNING: Service runner-fa6cab46-project-9021816-concurrent-0-docker-0 probably didn't start properly.
Health check error:
service "runner-fa6cab46-project-9021816-concurrent-0-docker-0-wait-for-service" timeout
Health check container logs:
Service container logs:
2019-11-12T20:07:28.918358216Z time="2019-11-12T20:07:28.908232827Z" level=info msg="Starting up"