Hi, @Johan Forssell! Welcome to the community!
We reviewed your request and, in order to properly assist you, could you please share some additional information regarding the issue you faced? Would it be possible for you to confirm to us:
The image name along with the tag name that you created in the first step;
The value of IMAGE_NAME and TAGS that you specified in the Pipe definition to push the image;
The error you received.
Please, feel free to share any additional information regarding this case. Thank you.
First, I used docker build --tag to build a docker image using my whole private repo name
The I run the atlassian/aws-ecr-push-image:1.4.2 pipe
INFO: Executing the aws-ecr-push-image pipe...
INFO: Successfully logged in to https://123456789012.dkr.ecr.eu-west-1.amazonaws.com
✖ Image not found: 404 Client Error: Not Found ("no such image: bla/server: No such image: bla/server:latest")
I took this to indicate some kind of AWS ECR problem, which is not the case.
I was simply tagging my docker image wrong.
name: Build and publish latest image
- make docker
- pipe: atlassian/aws-ecr-push-image:1.4.2
Please add a sentence that the docker image which is the INPUT to the pipe should be called simple/name:latest.
No full repo url, no other tag than latest.
Thanks for getting back to us! Checking the README of aws-ecr-push-image, we can see the following information:
The name of the image to push to the ECR. The name should be the same as your ECR repository name (example:
my-ecr-image). Remember that you don't need to add your registry URL in front of the image name, the pipe will fetch this URL from AWS and add it for you. Don't add tag in the IMAGE_NAME variable, pass variables
TAGSinstead (see more information below).
So this information is described there. In this case, just to make sure we are on the same page, would you still like to add something else?
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...