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 permission denied

Folke Byfors

Hello,

I get the following error in my pipeline when using slack-notify .

+ docker container run \

--volume=/opt/atlassian/pipelines/agent/build:/opt/atlassian/pipelines/agent/build \

--volume=/usr/local/bin/docker:/usr/local/bin/docker:ro \

--volume=/opt/atlassian/pipelines/agent/ssh:/opt/atlassian/pipelines/agent/ssh:ro \

<span>--volume=/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes:/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes \</span>

<span>--volume=/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/atlassian/slack-notify:/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/atlassian/slack-notify \</span>

--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_PROJECT_UUID="$BITBUCKET_PROJECT_UUID" \

--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_BRANCH="$BITBUCKET_BRANCH" \

--env=BITBUCKET_REPO_UUID="$BITBUCKET_REPO_UUID" \

--env=BITBUCKET_PROJECT_KEY="$BITBUCKET_PROJECT_KEY" \

--env=BITBUCKET_REPO_SLUG="$BITBUCKET_REPO_SLUG" \

--env=CI="$CI" \

--env=BITBUCKET_REPO_OWNER="$BITBUCKET_REPO_OWNER" \

--env=BITBUCKET_STEP_RUN_NUMBER="$BITBUCKET_STEP_RUN_NUMBER" \

--env=BITBUCKET_BUILD_NUMBER="$BITBUCKET_BUILD_NUMBER" \

--env=BITBUCKET_GIT_SSH_ORIGIN="$BITBUCKET_GIT_SSH_ORIGIN" \

--env=BITBUCKET_PIPELINE_UUID="$BITBUCKET_PIPELINE_UUID" \

--env=BITBUCKET_COMMIT="$BITBUCKET_COMMIT" \

--env=BITBUCKET_CLONE_DIR="$BITBUCKET_CLONE_DIR" \

--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" \

<span>--env=BITBUCKET_PIPE_SHARED_STORAGE_DIR="/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes" \</span>

<span>--env=BITBUCKET_PIPE_STORAGE_DIR="/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/atlassian/slack-notify" \</span>

--env=MESSAGE="$BITBUCKET_TRIGGERER_USERNAME - $COMMIT_MESSAGE 

$LINK 

This will be in the next release." \

<span>--env=WEBHOOK_URL="<a href="https://hooks.slack.com/services/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" rel="noopener nofollow noreferrer" target="_blank">https://hooks.slack.com/services/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</a>" \</span>

--add-host="host.docker.internal:$BITBUCKET_DOCKER_HOST_INTERNAL" \

bitbucketpipelines/slack-notify:2.0.0

<span>/tmp/e5021ecc-2427-51f0-ad65-08124a7fd8a5/tmp/shellScript1224050314865190000.sh: line 54: docker: Permission denied</span>

This is what pipe that gives the error in bitbucket-pipeline.yml

- step: &send-to-slack-merge

name: Send to slack merge

runs-on:

- qbank3.runner

image:

name: eu.gcr.io/qbnk-cloud/qbank3/phpfpm:1.2.5-alpine

username: _json_key

password: '$GCLOUD_API_JSON'

script:

- COMMIT_MESSAGE=`git log --format=%B -n 1 $BITBUCKET_COMMIT`

- export foundTicket=$(echo $COMMIT_MESSAGE | grep -oE '([a-zA-Z]{2,}[-]{1}[0-9]{1,})')

- if [[ $foundTicket ]]; then export LINK=$ANOTHERURL/$foundTicket}; else export LINK=$URL; fi

- export BITBUCKET_TRIGGERER_USERNAME=$(curl -X GET -g "https://api.bitbucket.org/2.0/users/${BITBUCKET_STEP_TRIGGERER_UUID}" | jq -r ."display_name")

- pipe: atlassian/slack-notify:2.0.0

variables:

WEBHOOK_URL: $WEBHOOK

MESSAGE: "$BITBUCKET_TRIGGERER_USERNAME - $COMMIT_MESSAGE \n$LINK \nThis will be in the next release."

I am using my own runner, could that be the issue? I don't understand why Docker does not have permission!?

Accepted answers

All comments

There are no accepted answers yet

Welcome!

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

Quick Links

Find more posts tagged with

cloud

bitbucket-pipelines

slack

bitbucket-runners