serverless-deploy build failed - Unable to find image

[Milad Rezazadeh]

Bitbucket-pipelines are failing due to below error, apparently it's not able to pull the latest image. 

bitbucketpipelines/serverless-deploy:0.1.6Unable to find image 'bitbucketpipelines/serverless-deploy:0.1.6' locally0.1.6: Pulling from bitbucketpipelines/serverless-deploy

There is not much documentation about it as well, Anyone experience this issue ? 

[Milad Rezazadeh]

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.6Unable to find image 'bitbucketpipelines/serverless-deploy:0.1.6' locally0.1.6: Pulling from bitbucketpipelines/serverless-deploy8559a31e96f4: Pulling fs layer62e60f3ef11e: Pulling fs layer286adfd1ee25: Pulling fs layer8973789a3a6b: Pulling fs layer9b8d369425a7: Pulling fs layer1880b587dc11: Pulling fs layer28c0ea6c8f0c: Pulling fs layer9aad93b64af0: Pulling fs layer5b5c68f3e4f3: Pulling fs layer1880b587dc11: Waiting28c0ea6c8f0c: Waiting9aad93b64af0: Waiting5b5c68f3e4f3: Waiting9b8d369425a7: Waiting8973789a3a6b: Waiting62e60f3ef11e: Verifying Checksum62e60f3ef11e: Download complete286adfd1ee25: Verifying Checksum286adfd1ee25: Download complete8559a31e96f4: Verifying Checksum8559a31e96f4: Download complete8973789a3a6b: Verifying Checksum8973789a3a6b: Download complete9b8d369425a7: Verifying Checksum9b8d369425a7: Download complete28c0ea6c8f0c: Download complete5b5c68f3e4f3: Verifying Checksum5b5c68f3e4f3: Download complete9aad93b64af0: Verifying Checksum9aad93b64af0: Download complete8559a31e96f4: Pull complete62e60f3ef11e: Pull complete1880b587dc11: Verifying Checksum1880b587dc11: Download complete286adfd1ee25: Pull complete8973789a3a6b: Pull complete9b8d369425a7: Pull complete1880b587dc11: Pull complete28c0ea6c8f0c: Pull complete9aad93b64af0: Pull complete5b5c68f3e4f3: Pull completeDigest: sha256:dcadcf4634993e0a89881a426ad69daee451def272d135f28d96dde31be44611Status: Downloaded newer image for bitbucketpipelines/serverless-deploy:0.1.6INFO: 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 --------------------------------------------

[Halyna Berezovska]

@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.

[Halyna Berezovska]

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

[Halyna Berezovska]

@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...

[Halyna Berezovska]

Also, every pipe's repo has a documentation, please refer here .

Regards, Galyna

[Milad Rezazadeh]

Appreciate it ,  we did as documentation said, 

script: 
  - npm install 
  - pipe: atlassian/serverless-deploy:0.1.6
    variables: 
        ...