I created a Pipeline using my customer docker image, pulled from Docker Hub. Worked just fine.
Then I updated the Dockerfile for that image, adding PhantomJS. I pushed that new image to my Docker Hub repo. Just to make sure that a pull from that repo would give me the updated image, I deleted local Docker images and pulled it fresh from the repo using the same image name as in my bitbucket-pipelines.yml.
So, I'm confident that if the Pipeline were re-pulling/refreshing the Docker image from Docker Hub, it would get the update.
However, when the Pipeline runs, it fails for lack of "phantomjs"—the very thing I added to the Docker image and verified.
So, how I can guarantee that the Pipeline pulls the latest docker image from my Docker Hub repo?
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