Question on GitLab deployment

[jamesthesken]

Question on GitLab deployment

[dorinclisu]

The CI config uses the docker-in-docker service (docker:19.03.12-dind), which is highly recommended against BTW.

What it means in your case is that any docker commands will get serviced by the inner docker daemon, which is independent and has nothing to do with the outer daemon (the swarm master), hence the error.

If you installed the runner per instructions (and /var/run/docker.sock is bind mounted) then you should simply remove the dind service from the CI yaml and it will probably work.

[HongQuan195]

this node is not a swarm manager. Use "docker swarm init"

Hi @dorinclisu @tiangolo have any suggest for this problem?

[jamesthesken]

Hi @tiangolo , any thoughts?

[jamesthesken]

Hey @dorinclisu thank you for your reply, I was feeling like I couldn't get past this hurdle. I'll give that a try and report back.

Which CI yaml are you referring to? I don't see docker-in-docker service on this page: https://dockerswarm.rocks/gitlab-ci/

[dorinclisu]

services:
    - docker:19.03.12-dind

This is the service I'm talking about, defined in your .gitlab-ci.yml. Delete that.

[derek-mba]

The CI config uses the docker-in-docker service (docker:19.03.12-dind), which is highly recommended against BTW.

Unfortunately, it is not "highly recommended against" by GitLab

If you installed the runner per instructions (and /var/run/docker.sock is bind mounted) then you should simply remove the dind service from the CI yaml and it will probably work.

If you installed the runner "per instructions" you probably are running the docker-in-docker service! It does mention socket binding, but there's a note "If you bind the Docker socket and you are using GitLab Runner 11.11 or later, you can no longer use docker:20.10.16-dind as a service.", which seems to imply this is a bad thing. Having now read your reference, I can see I have zero need for the dind service, but I sure wish GitLab would make that clear.

[tiangolo]

Thanks for the patience!

I should let you know, that I had to deprecate this website and ideas, I would no longer recommend Docker Swarm Mode for new projects: https://dockerswarm.rocks/swarm-or-kubernetes/ 🥲

[github-actions]

Assuming the original issue was solved, it will be automatically closed now. But feel free to add more comments or create new issues.

[HongQuan195]

have same issue. here is my ci pipeline. Build stage is fine but deploy get issue related to swarm master node. I remove services as [dorinclisu] recommend but still not working. It stuck in curl -kvv step
.gitlab-ci.yml

variables:

before_script:

• docker info
• docker --version

stages:

• build
• deploy

include:

• script/ci-build.yml
• script/ci-staging.yml

script/ci-build.yml

BUILD:
stage: build
image: docker:dind
tags:
- gcp
- aai
before_script:
- echo "$DOCKER_REGISTRY_PASSWORD" | docker login $DOCKER_REGISTRY_URL --username $DOCKER_REGISTRY_USER --password-stdin
script:
- export CONTAINER_IMAGE=$DOCKER_REGISTRY_URL/$DOCKER_IMAGE_NAME:$IMAGE_TAG
- docker build -t $CONTAINER_IMAGE .
- docker image push $CONTAINER_IMAGE
- docker rmi $CONTAINER_IMAGE
only:
- fix-runner-gitlab-ci

script/ci-staging.yml
STA - DEPLOY:
stage: deploy
image: docker:dind
tags:
- gcp
before_script:
- apk add curl
- apk add gettext
variables:
NETWORK: public
script:
- echo $IMAGE_TAG
- envsubst < ./script/stack.yml > ./deploy-content.yml
- content_with_backslash=$(awk '{printf "%s\n", $0}' deploy-content.yml)
- printf "%s" "$content_with_backslash"
- |
curl -kvv --fail-with-body --location --request PUT 'https://abc'
--header "x-api-key: $DEPLOYMENT_TOKEN_STAGING"
--header "Content-Type: application/json"
--data "{
"prune": true,
"pullImage": true,
"stackFileContent": "$content_with_backslash"
}"
only:
- fix-runner-gitlab-ci