Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Unable to find image 'bitbucketpipelines/aws-code-deploy:0.2.1' locally

Unable to find image 'bitbucketpipelines/aws-code-deploy:0.2.1' locally

1 answer

This just means that the 'bitbucketpipelines/aws-code-deploy' image version 0.2.1 has not yet been downloaded to your system, which usually happens automatically depending on how you invoke Docker - here's an example when I try to run this image:

λ docker run --rm -it bitbucketpipelines/aws-code-deploy:0.2.1
Unable to find image 'bitbucketpipelines/aws-code-deploy:0.2.1' locally
0.2.1: Pulling from bitbucketpipelines/aws-code-deploy
c67f3896b22c: Already exists
410e0473b28d: Already exists
6fca03832078: Pull complete
Digest: sha256:35b090f2fad506eff59c272d7becb57918f0fa04c3a9780faeb1074e84d2e3a0
Status: Downloaded newer image for bitbucketpipelines/aws-code-deploy:0.2.1
/usr/bin/pipe.sh: line 80: AWS_ACCESS_KEY_ID: AWS_ACCESS_KEY_ID variable missing.

As you can see, I got the same informal message and Docker then proceeded to download the image from the public Docker registry. Any subsequent run will not show the message again, because the image has now been cached on the system:

λ docker run --rm -it bitbucketpipelines/aws-code-deploy:0.2.1
/usr/bin/pipe.sh: line 80: AWS_ACCESS_KEY_ID: AWS_ACCESS_KEY_ID variable missing.

Docker now just runs the readily available cached image as desired (and the pipe just fails, because I do not have the expected environment variables on my local system).

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

712 views 15 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you