docker command not available in custom pipe for BitBucket Pipeline

user_2532203 0
Viewed 210

I'm working on a build step that handles common deployment tasks in a Docker Swarm Mode cluster. As this is a common problem for us and for others, we've shared this build step as a BitBucket pipe: https://bitbucket.org/matchory/swarm-secret-pipe/ The pipe needs to use the docker command to work with a remote Docker installation. This doesn't work, however, because the docker executable cannot be found when the pipe runs.

The following holds true for our test repository pipeline:

  • The docker option is set to true: 
    options:
  docker: true
  • The docker service is enabled for the build step: 
    main:
  - step:
    services:
      - docker: true
  • Docker works fine in the repository pipeline itself, but not within the pipe.
  • Pipeline log shows the docker path being mounted into the pipe container:
    docker container run \
  --volume=/opt/atlassian/pipelines/agent/build:/opt/atlassian/pipelines/agent/build \
  --volume=/opt/atlassian/pipelines/agent/ssh:/opt/atlassian/pipelines/agent/ssh:ro \
  --volume=/usr/local/bin/docker:/usr/local/bin/docker:ro \
  --volume=/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes:/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes \
  --volume=/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/matchory/swarm-secret-pipe:/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/matchory/swarm-secret-pipe \
  --workdir=$(pwd) \
  --label=org.bitbucket.pipelines.system=true \
  radiergummi/swarm-secret-pipe:1.3.7@sha256:baf05b25b38f2a59b044e07f4ad07065de90257a000137a0e1eb71cbe1a438e5

The pipe is pretty standard and uses a recent Alpine image; nothing special in that regard. The PATH is never overwritten. Now for the fun part: If I do ls /usr/local/bin/docker inside the pipe, it shows an empty directory:

ls /usr/local/bin
total 16K 
drwxr-xr-x 1 root root 4.0K May 13 13:06 .
drwxr-xr-x 1 root root 4.0K Apr 4 16:06 ..
drwxr-xr-x 2 root root 4.0K Apr 29 09:30 docker
ls /usr/local/bin/docker
total 8K 
drwxr-xr-x 2 root root 4.0K Apr 29 09:30 .
drwxr-xr-x 1 root root 4.0K May 13 13:06 ..
ls: /usr/local/bin/docker/docker: No such file or directory

As far as I understand pipelines and Docker, /usr/local/bin/docker should be the docker binary file. Instead, it appears to be an empty directory for some reason. What is going on here?

I've also looked at other, official, pipes. They don't do anything differently, but seem to be using the docker command just fine (eg. the Azure pipe).

bitbucket-pipelines docker
1 Answers

After talking to BitBucket support, I solved the issue. As it turns out, if the docker context is changed, any docker command is sent straight to the remote docker binary, which (on our services) lives at a different path than in BitBucket Pipelines!
As we changed the docker context before using the pipe, and the docker instance mounted into the pipe still has the remote context set, but the pipe searches for the docker binary at another place, the No such file or directory error is thrown.

TL;DR: Always restore the default docker host/context before passing control to a pipe, e.g.:

script:
  - export DEFAULT_DOCKER_HOST=$DOCKER_HOST
  - unset DOCKER_HOST
  - docker context create remote --docker "host=ssh://${DEPLOY_SSH_USER}@${DEPLOY_SSH_HOST}"
  - docker context use remote

  # do your thing

  - export DOCKER_HOST=$DEFAULT_DOCKER_HOST # <------ restore the default host
  - pipe: matchory/swarm-secret-pipe:1.3.16
user_25322030
Related