Closed fergyfresh closed 6 years ago
Hi,
can you please show me the relevant part of your .gitlab-ci.yml?
This is how the relevant part looks in my case:
.docker: &docker
image: tmaier/docker-compose:latest
services:
- docker:dind
before_script:
- |
if [ -z "$DOCKER_HOST" -a "$KUBERNETES_PORT" ]; then
export DOCKER_HOST='tcp://localhost:2375'
fi
- docker login -u "$CI_REGISTRY_USER" -p "$CI_REGISTRY_PASSWORD" $CI_REGISTRY
- printenv >> .env.test
variables: &docker_variables
DOCKER_DRIVER: overlay2
Looks almost the same, only different is I don't have that bash if statement.
Also I think my DOCKER_HOST=tcp://docker:2375
, which used to work about 3 weeks ago.
Very interesting though, I appreciate the quick feedback. I already have some things to try and I'm excited to get to the bottom of this.
THAT WORKED!!!!! Using your
before_script:
- |
if [ -z "$DOCKER_HOST" -a "$KUBERNETES_PORT" ]; then
export DOCKER_HOST='tcp://localhost:2375'
fi
I had DOCKER_HOST set to tcp://docker:2375
, like I did for the non-docker-compose stuff, but for some reason that environment variable was blank here.
But it 100% worked like a month ago, did you recently implement this workaround?
I use this for quite some time. It is relevant when the runner uses kubernetes instead of docker-machine or plain docker. So it depends on which gitlab-runner you use...
I see. But I am seeing this issue using gitlab-runner on gitlab itself using version gitlab-runner-11.4.0.rc1
I don’t know. Maybe they use kubernetes as well.. this would actually make sense, as they moved to Google Cloud.
Is there any topic left or can we close this issue?
I can pull and push docker containers in gitlab ci, but when i use this latest container i cannot push/pull with gitlab's newest runner updates.