Hi all, I'm new to pipelines, so probably am doing very obviously wrong. I'm starting out simple, and basically copying the templates provided. image: node:16 pipelines: branches: master: - step: name: Test script: - cd Server/Source - npm install - npm test - step: name: Pre-Deploy script: - pipe: atlassian/ssh-run:0.4.0 variables: SSH_USER: 'root' SERVER: '31.220.31.93' SSH_KEY: $ssh_key MODE: 'command' COMMAND: '/root/dir/pre-deploy.sh' # path to a script in your repository The `test` step executes without a problem. However, I can't run the ssh command Help, please? :) + 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/atlassian/ssh-run:/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/atlassian/ssh-run \ --workdir=$(pwd) \ --label=org.bitbucket.pipelines.system=true \ --env=BITBUCKET_STEP_TRIGGERER_UUID="$BITBUCKET_STEP_TRIGGERER_UUID" \ --env=BITBUCKET_REPO_FULL_NAME="$BITBUCKET_REPO_FULL_NAME" \ --env=BITBUCKET_GIT_HTTP_ORIGIN="$BITBUCKET_GIT_HTTP_ORIGIN" \ --env=BITBUCKET_REPO_SLUG="$BITBUCKET_REPO_SLUG" \ --env=BITBUCKET_PROJECT_UUID="$BITBUCKET_PROJECT_UUID" \ --env=CI="$CI" \ --env=BITBUCKET_REPO_OWNER="$BITBUCKET_REPO_OWNER" \ --env=BITBUCKET_REPO_IS_PRIVATE="$BITBUCKET_REPO_IS_PRIVATE" \ --env=BITBUCKET_WORKSPACE="$BITBUCKET_WORKSPACE" \ --env=BITBUCKET_REPO_OWNER_UUID="$BITBUCKET_REPO_OWNER_UUID" \ --env=BITBUCKET_STEP_RUN_NUMBER="$BITBUCKET_STEP_RUN_NUMBER" \ --env=BITBUCKET_BUILD_NUMBER="$BITBUCKET_BUILD_NUMBER" \ --env=BITBUCKET_BRANCH="$BITBUCKET_BRANCH" \ --env=BITBUCKET_GIT_SSH_ORIGIN="$BITBUCKET_GIT_SSH_ORIGIN" \ --env=BITBUCKET_PIPELINE_UUID="$BITBUCKET_PIPELINE_UUID" \ --env=BITBUCKET_COMMIT="$BITBUCKET_COMMIT" \ --env=BITBUCKET_REPO_UUID="$BITBUCKET_REPO_UUID" \ --env=BITBUCKET_CLONE_DIR="$BITBUCKET_CLONE_DIR" \ --env=BITBUCKET_PROJECT_KEY="$BITBUCKET_PROJECT_KEY" \ --env=PIPELINES_JWT_TOKEN="$PIPELINES_JWT_TOKEN" \ --env=BITBUCKET_STEP_UUID="$BITBUCKET_STEP_UUID" \ --env=BITBUCKET_DOCKER_HOST_INTERNAL="$BITBUCKET_DOCKER_HOST_INTERNAL" \ --env=DOCKER_HOST="tcp://host.docker.internal:2375" \ --env=BITBUCKET_PIPE_SHARED_STORAGE_DIR="/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes" \ --env=BITBUCKET_PIPE_STORAGE_DIR="/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/atlassian/ssh-run" \ --env=COMMAND="/root/squawker/pre-deploy.sh" \ --env=MODE="command" \ --env=SERVER="31.220.31.93" \ --env=SSH_KEY="$ssh_key" \ --env=SSH_USER="root" \ --add-host="host.docker.internal:$BITBUCKET_DOCKER_HOST_INTERNAL" \ bitbucketpipelines/ssh-run:0.4.0 Unable to find image 'bitbucketpipelines/ssh-run:0.4.0' locally

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; } } }

Unable to find image 'bitbucketpipelines/ssh-run:0.4.0' locally

capsicumdreams

Hi all,

I'm new to pipelines, so probably am doing very obviously wrong.
I'm starting out simple, and basically copying the templates provided.

image: node:16

pipelines:

  branches:

    master:

      - step:

          name: Test

          script:

            - cd Server/Source

            - npm install

            - npm test

      - step:

          name: Pre-Deploy

          script:

            - pipe: atlassian/ssh-run:0.4.0

              variables:

                SSH_USER: 'root'

                SERVER: '31.220.31.93'

                SSH_KEY: $ssh_key

                MODE: 'command'

                COMMAND: '/root/dir/pre-deploy.sh' # path to a script in your repository

The `test` step executes without a problem.
However, I can't run the ssh command

Help, please?

+ 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/atlassian/ssh-run:/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/atlassian/ssh-run \
--workdir=$(pwd) \
--label=org.bitbucket.pipelines.system=true \
--env=BITBUCKET_STEP_TRIGGERER_UUID="$BITBUCKET_STEP_TRIGGERER_UUID" \
--env=BITBUCKET_REPO_FULL_NAME="$BITBUCKET_REPO_FULL_NAME" \
--env=BITBUCKET_GIT_HTTP_ORIGIN="$BITBUCKET_GIT_HTTP_ORIGIN" \
--env=BITBUCKET_REPO_SLUG="$BITBUCKET_REPO_SLUG" \
--env=BITBUCKET_PROJECT_UUID="$BITBUCKET_PROJECT_UUID" \
--env=CI="$CI" \
--env=BITBUCKET_REPO_OWNER="$BITBUCKET_REPO_OWNER" \
--env=BITBUCKET_REPO_IS_PRIVATE="$BITBUCKET_REPO_IS_PRIVATE" \
--env=BITBUCKET_WORKSPACE="$BITBUCKET_WORKSPACE" \
--env=BITBUCKET_REPO_OWNER_UUID="$BITBUCKET_REPO_OWNER_UUID" \
--env=BITBUCKET_STEP_RUN_NUMBER="$BITBUCKET_STEP_RUN_NUMBER" \
--env=BITBUCKET_BUILD_NUMBER="$BITBUCKET_BUILD_NUMBER" \
--env=BITBUCKET_BRANCH="$BITBUCKET_BRANCH" \
--env=BITBUCKET_GIT_SSH_ORIGIN="$BITBUCKET_GIT_SSH_ORIGIN" \
--env=BITBUCKET_PIPELINE_UUID="$BITBUCKET_PIPELINE_UUID" \
--env=BITBUCKET_COMMIT="$BITBUCKET_COMMIT" \
--env=BITBUCKET_REPO_UUID="$BITBUCKET_REPO_UUID" \
--env=BITBUCKET_CLONE_DIR="$BITBUCKET_CLONE_DIR" \
--env=BITBUCKET_PROJECT_KEY="$BITBUCKET_PROJECT_KEY" \
--env=PIPELINES_JWT_TOKEN="$PIPELINES_JWT_TOKEN" \
--env=BITBUCKET_STEP_UUID="$BITBUCKET_STEP_UUID" \
--env=BITBUCKET_DOCKER_HOST_INTERNAL="$BITBUCKET_DOCKER_HOST_INTERNAL" \
--env=DOCKER_HOST="tcp://host.docker.internal:2375" \
--env=BITBUCKET_PIPE_SHARED_STORAGE_DIR="/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes" \
--env=BITBUCKET_PIPE_STORAGE_DIR="/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/atlassian/ssh-run" \
--env=COMMAND="/root/squawker/pre-deploy.sh" \
--env=MODE="command" \
--env=SERVER="31.220.31.93" \
--env=SSH_KEY="$ssh_key" \
--env=SSH_USER="root" \
--add-host="host.docker.internal:$BITBUCKET_DOCKER_HOST_INTERNAL" \
bitbucketpipelines/ssh-run:0.4.0
Unable to find image 'bitbucketpipelines/ssh-run:0.4.0' locally

Accepted answers

Syahrul

Hi @capsicumdreams

Apologize for the confusion, the error you mention "Unable to find image 'bitbucketpipelines/ssh-run:0.4.0' locally" is a completely fine error as the pipe is not stored locally so it won't be able to find it hence the error.
The build will then proceed to download the image from Docker afterward so you can safely ignore the error.

Now as for why the pipe did not trigger the SSH commands, I would suggest you enable the debug mode in the pipe to get more information. Below are an example of enabling the debug mode:

script:
  - pipe: atlassian/ssh-run:0.4.0
    variables:
      SSH_USER: 'ec2-user'
      SERVER: '127.0.0.1'
      COMMAND: 'echo $HOSTNAME'
      DEBUG: true

Once you get the output, feel free to share it here if you can't find out why it's failing, but do filter out any sensitive information first before sharing.

Cheers,
Syahrul

capsicumdreams

@Syahrulwas right - I changed how I supplied the SSH key., and it runs fine, now.
I'd prefer there was a nicer error message, but it's all functional.

Thanks 👍

All comments

Syahrul

Hi @capsicumdreams

Now as for why the pipe did not trigger the SSH commands, I would suggest you enable the debug mode in the pipe to get more information. Below are an example of enabling the debug mode:

script:
  - pipe: atlassian/ssh-run:0.4.0
    variables:
      SSH_USER: 'ec2-user'
      SERVER: '127.0.0.1'
      COMMAND: 'echo $HOSTNAME'
      DEBUG: true

Once you get the output, feel free to share it here if you can't find out why it's failing, but do filter out any sensitive information first before sharing.

Cheers,
Syahrul

capsicumdreams

Thanks, Syahrul,

I've spent 45 minutes trying to type out a reply - but it complains that I'm sending the same message too often.
"Update your text, or wait before reposting."

I have done both. For over half an hour, so far.

Infuriating.

Here is a Onedrive link to a reply that isn't blocked by your overly-ambitious spam system.

https://1drv.ms/t/s!AkuYD2UOMAw_iqwzZBtMfET6kmdJAQ?e=Yy0qHE

Thanks a lot for trying to help..

Syahrul

Hey @capsicumdreams ,

G'Day!

Sorry to hear you are having an issue with the community text post, most likely an issue with too many logs to share.

I try opening the link but it's empty for me without any logs/data could you check and confirm that or share using another alternate method such as google drive etc?

Thanks,
Syahrul

capsicumdreams

Having serious difficulty even responding using this editor.
Do you guys need some software engineers?

capsicumdreams

there is no html!!

capsicumdreams

@Syahrulwas right - I changed how I supplied the SSH key., and it runs fine, now.
I'd prefer there was a nicer error message, but it's all functional.

Thanks 👍

Welcome!

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

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

atl-gruland

ssh