Closed david-nano closed 5 months ago
Please, get rid of as many factors and yaml as possible.
This is not an as simple as possible example at all 😁
It makes it overly difficult for others to debug.
Please, get rid of as many factors and yaml as possible.
This is not an as simple as possible example at all 😁
It makes it overly difficult for others to debug.
Is it better now?
---
test-job:
image: docker:24.0.2-git
services:
- name: registry.hub.docker.com/library/docker:24.0.2-dind
alias: docker
script:
- docker version
Using this .gitlab-ci-local-env
PRIVILEGED=true
ULIMIT=8000:16000
VOLUME="/etc/docker/daemon.json:/etc/docker/daemon.json certs:/certs/client /netapp:/netapp"
VARIABLE="DOCKER_TLS_CERTDIR=/certs DOCKER_BUILDKIT=0 COMPOSE_DOCKER_CLI_BUILD=0"
I'm not seeing the symptom, when using a simple example.
https://gitlab.com/firecow/gitlab-ci-debugging/-/jobs/6254313223
Strip down your example, line by line, instruction by instruction, and eventually I'm sure we will get to the bottom of this.
I would be nice to add some sort of hint for others that might end up in a similar situation. What was your mistake?
I would be nice to add some sort of hint for others that might end up in a similar situation. What was your mistake?
Not reproducible :( The next business day, everything worked, not sure why.
TL;DR - same job template, each one use different
docker-compose.yaml
, one is working fine, and one is getting errors during DIND injection.Minimal .gitlab-ci.yml illustrating the issue
Expected behavior getting test working
Host information Ubuntu 22.04 gitlab-ci-local 4.46.1
Containerd binary docker
Additional context I have two jobs which use the same template job, one is using docker compose A, and the other docker compose B. The one that use compose A, is finish successfully, the other one fail with error:
Compose a:
compose b:
My
.gitlab-ci-local-env
file: