My dockerfile extends an image hosted in a private repo in hub.docker.com:
When building, pipeline fails with:
+ docker build -t $IMAGE_NAME .
Sending build context to Docker daemon 37.27MB
Step 1/11 : FROM myprivaterepo/image:latest
repository myprivaterepo/image not found: does not exist or no pull access
How could I extend my image with private images?
Duh... turns out I had `docker login` missplaced.
For anyone interested in the topic:
# Set $DOCKER_HUB_USERNAME and $DOCKER_HUB_PASSWORD as environment variables in repository settings
- export IMAGE_NAME=myprivaterepo/image:latest
- docker login --username $DOCKER_HUB_USERNAME --password $DOCKER_HUB_PASSWORD
- docker build -t $IMAGE_NAME .
- docker push $IMAGE_NAME
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs