nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"docker: command not found" error when running code-deploy pipe

Julien Richard-Foy

I’ve copied the `script` entry given in the documentation of the atlassian/aws-code-deploy pipe and adapted to my needs:

pipelines:
  branches:
master:
      - step:
name: Build
image: node:10
        script:
          - ...
      - step:
name: Deploy
script:
- pipe: atlassian/aws-code-deploy:0.2.1
variables:
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY
AWS_DEFAULT_REGION: 'us-east-2'
APPLICATION_NAME: $APPLICATION_NAME
COMMAND: 'upload'
ZIP_FILE: $ZIP_FILE
S3_BUCKET: $S3_BUCKET

When the pipeline is run, I get the following error:

<span><br>    --volume=/opt/atlassian/pipelines/agent/build:/opt/atlassian/pipelines/agent/build \</span><span><br>    --volume=/opt/atlassian/pipelines/agent/ssh:/opt/atlassian/pipelines/agent/ssh:ro \<br>      ...</span><span><br>bash: docker: command not found</span><span> docker container run \</span>

My pipeline is using the default Docker image.

Accepted answers

Julien Richard-Foy

I was able to fix the problem by adding the `docker` service to my step:

 - step:
name: Deploy
services:
   - docker
script:
- pipe: atlassian/aws-code-deploy:0.2.1
variables:
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
         ...

All comments

Samuell

I had same issue i just reruned pipelines again and it works.

Julien Richard-Foy

I was able to fix the problem by adding the `docker` service to my step:

 - step:
name: Deploy
services:
   - docker
script:
- pipe: atlassian/aws-code-deploy:0.2.1
variables:
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
         ...

Xinyi Xu

Hey, accepted answer doesn't work for me. I was able to make it run adding optioins:docker: true to the end. See below

pipelines:
  branches:
master:
      - step:
name: Build
image: node:10
        script:
          - ...
      - step:
name: Deploy
script:
- pipe: atlassian/aws-code-deploy:0.2.1
variables:
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY
AWS_DEFAULT_REGION: 'us-east-2'
APPLICATION_NAME: $APPLICATION_NAME
COMMAND: 'upload'
ZIP_FILE: $ZIP_FILE
S3_BUCKET: $S3_BUCKET

options:
  docker: true

helgispbru

I have the same issue and this solutions doesn't help me.

Dipesh Rane

pipelines:
  branches:
master:
      - step:
name: Build
image: node:10
        script:
          - ...
      - step:
        services:
         - docker
name: Deploy
script:
- pipe: atlassian/aws-code-deploy:0.2.1
variables:
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY
AWS_DEFAULT_REGION: 'us-east-2'
APPLICATION_NAME: $APPLICATION_NAME
COMMAND: 'upload'
ZIP_FILE: $ZIP_FILE
S3_BUCKET: $S3_BUCKET

Dipesh Rane

add docker as services it will fix the issue

Peter_vrmaz4

You must have a reserved Variable called PATH, in your enviroment.

Radu Cristescu

For me, this was caused by BCLOUD-22851. I have self-hosted runners where this error happens once in a blue moon.

I have a cron job on the lookout for this bug. For each runner, it looks for the `docker` directory. If it finds it, it stops the runner, removes the directory, and starts the runner again.

Unfortunately, a pipeline has to trigger the problem before the workaround kicks in, so the pipeline that triggers it will fail. But because the workaround kicks in automatically via cron, rerunning the pipeline will be fine.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket-pipelines

aws