Menu
gitlab CI docker stalls after 2min
slight code change and same bug across different repos. Ci/CD used to work on these repos?
...
Step 4/11 : RUN yarn install
---> Using cache
---> c75197e0dbaa
Step 5/11 : COPY babel.config.js babel.config.js
---> Using cache
---> 482b1ff64322
Step 6/11 : COPY src src
---> d530de056b88
Step 7/11 : RUN mkdir locales
---> Running in f7885ea9a3c3
...
Link to the GL issue https://gitlab.com/gitlab-com/support-forum/issues/5202
997
You can use GitLab CI/CD with Docker to create Docker images. For example, you can create a Docker image of your application, test it, and publish it to a container registry. To run Docker commands in your CI/CD jobs, you must configure GitLab Runner to support docker commands.
You can also check if your runner is allowed to run untagged jobs - you can do that under Admin and then edit it to see if that option is enabled. The runner is a specific runner for the project and not a shared one.
gitlab/dind is image that should be used to build projects with docker-based workflow. The image runs Docker Engine and includes Docker Compose which allows to use full docker toolkit from build script. docker pull gitlab/dind. © 2022 Docker Inc.
GitLab Runner implements a number of executors that can be used to run your build. It determines the environment each job runs in. For example, If I want CI/CD job to run PowerShell commands, I might install GitLab Runner on a server and then register a runner that uses the shell executor.
This is a known issue on gitlab. Change dind service as follows. That should fix your problem.
services:
- docker:19.03.5-dind
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
