Bitbucket-pipelines are failing due to below error, apparently it's not able to pull the latest image.
bitbucketpipelines/serverless-deploy:0.1.6
Unable to find image 'bitbucketpipelines/serverless-deploy:0.1.6' locally
0.1.6: Pulling from bitbucketpipelines/serverless-deploy
There is not much documentation about it as well, Anyone experience this issue ?
bitbucket-pipelines.yml
image: node:10.15.3
pipelines:
tags:
release-*:
- step:
name: Build and release tag
script:
- npm install
- pipe: atlassian/serverless-deploy:0.1.6
variables:
AWS_ACCESS_KEY_ID: $AWS_LAMBDA_KEY_PROD
AWS_SECRET_ACCESS_KEY: $AWS_LAMBDA_SECRET_PROD
EXTRA_ARGS: -v --stage prod --region $AWS_LAMBDA_REGION_PROD
the full error we see is as below,
+ 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/serverless-deploy:/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/atlassian/serverless-deploy \
--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" \
--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/serverless-deploy" \
--env=AWS_ACCESS_KEY_ID="$AWS_LAMBDA_KEY_DEV0" \
--env=AWS_SECRET_ACCESS_KEY="$AWS_LAMBDA_SECRET_DEV0" \
--env=CONFIG="configs/serverless-dev0-$AWS_LAMBDA_REGION_DEV0.yml" \
--env=EXTRA_ARGS="-v --stage dev0 --region $AWS_LAMBDA_REGION_DEV0 --config configs/serverless-dev0-$AWS_LAMBDA_REGION_DEV0.yml" \
--add-host="host.docker.internal:$BITBUCKET_DOCKER_HOST_INTERNAL" \
bitbucketpipelines/serverless-deploy:0.1.6
Unable to find image 'bitbucketpipelines/serverless-deploy:0.1.6' locally
0.1.6: Pulling from bitbucketpipelines/serverless-deploy
8559a31e96f4: Pulling fs layer
62e60f3ef11e: Pulling fs layer
286adfd1ee25: Pulling fs layer
8973789a3a6b: Pulling fs layer
9b8d369425a7: Pulling fs layer
1880b587dc11: Pulling fs layer
28c0ea6c8f0c: Pulling fs layer
9aad93b64af0: Pulling fs layer
5b5c68f3e4f3: Pulling fs layer
1880b587dc11: Waiting
28c0ea6c8f0c: Waiting
9aad93b64af0: Waiting
5b5c68f3e4f3: Waiting
9b8d369425a7: Waiting
8973789a3a6b: Waiting
62e60f3ef11e: Verifying Checksum
62e60f3ef11e: Download complete
286adfd1ee25: Verifying Checksum
286adfd1ee25: Download complete
8559a31e96f4: Verifying Checksum
8559a31e96f4: Download complete
8973789a3a6b: Verifying Checksum
8973789a3a6b: Download complete
9b8d369425a7: Verifying Checksum
9b8d369425a7: Download complete
28c0ea6c8f0c: Download complete
5b5c68f3e4f3: Verifying Checksum
5b5c68f3e4f3: Download complete
9aad93b64af0: Verifying Checksum
9aad93b64af0: Download complete
8559a31e96f4: Pull complete
62e60f3ef11e: Pull complete
1880b587dc11: Verifying Checksum
1880b587dc11: Download complete
286adfd1ee25: Pull complete
8973789a3a6b: Pull complete
9b8d369425a7: Pull complete
1880b587dc11: Pull complete
28c0ea6c8f0c: Pull complete
9aad93b64af0: Pull complete
5b5c68f3e4f3: Pull complete
Digest: sha256:dcadcf4634993e0a89881a426ad69daee451def272d135f28d96dde31be44611
Status: Downloaded newer image for bitbucketpipelines/serverless-deploy:0.1.6
INFO: Deploying your serverless application...
Serverless Error ---------------------------------------
Got 2 config paths: [configs/serverless-dev0-$AWS_LAMBDA_REGION_DEV0.yml, configs/serverless-dev0-$AWS_LAMBDA_REGION_DEV0.yml].Expected single value
Get Support --------------------------------------------
@Milad Rezazadeh ah, so that actually found the image as I see in your full log.
Now you have problems with config:
Serverless Error ---------------------------------------
Got 2 config paths: [configs/serverless-dev0-$AWS_LAMBDA_REGION_DEV0.yml, configs/serverless-dev0-$AWS_LAMBDA_REGION_DEV0.yml].Expected single value
This fails because you have:
--env=CONFIG="configs/serverless-dev0-$AWS_LAMBDA_REGION_DEV0.yml" \
--env=EXTRA_ARGS="-v --stage dev0 --region $AWS_LAMBDA_REGION_DEV0 --config configs/serverless-dev0-$AWS_LAMBDA_REGION_DEV0.yml" \
You can see that we already have the variable CONFIG where it your config file is passed. But looks like it is also passing in EXTRA_ARGS (in your example usage however I don't see it, but also do not see your CONFIG variable passed, so I suspect you did not mention full example of pipe usage ).
But looking how the pipeline is running I can see clearly that extra arguments have option you don't need to provide:
--env=EXTRA_ARGS="-v --stage dev0 --region $AWS_LAMBDA_REGION_DEV0 --config configs/serverless-dev0-$AWS_LAMBDA_REGION_DEV0.yml"
Just remove --config option from extra args if you have such there.
Also I should say that for --verbose we have separate variabled called DEBUG: 'true'.
Contact us more in the case of more questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Seems like this is all, check you don't provide redundant arguments in EXTRA_ARGS variable, so it does not duplicate in AWS CLI when executing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Milad Rezazadeh please, provide us with pipe usage example in the pipeline.
I just tried it and it downloads the image in the pipeline.
Pull complete
Digest: sha256:***
Status: Downloaded newer image for bitbucketpipelines/serverless-deploy:0.1.6
INFO: Deploying your serverless application...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also, every pipe's repo has a documentation, please refer here .
Regards, Galyna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Appreciate it , we did as documentation said,
script:
- npm install
- pipe: atlassian/serverless-deploy:0.1.6
variables:
...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.