Docker tag is munged

Description:

I’m deploying an imaged based lambda function and specify the tag using the appropriate metadata in my template.yaml:

      DockerTag: v1
      DockerContext: ./function
      Dockerfile: Dockerfile

When this image is built using sam build, the docker image created adheres to the following name:

% docker images
REPOSITORY                                                TAG                     IMAGE ID            CREATED         SIZE
process                                                         v1                        4d8ff64bb5b8   20 hours ago   3.13GB

However, when sam deploy --guided is invoked, the following image name is used:

 % docker images
REPOSITORY                                                                                              TAG                                           IMAGE ID            CREATED        
  SIZE
8xxxxxxxxxx4.dkr.ecr.us-east-1.amazonaws.com/dev-scrb-process   process-4d8ff64bb5b8-v1   4d8ff64bb5b8   20 hours ago   3.13GB
process                                                         v1                        4d8ff64bb5b8   20 hours ago   3.13GB

Steps to reproduce:

Create a Docker image function to deploy with the metadata mentioned above.

Observed result:

See Description.

Expected result:

Shouldn’t the image push be: 8xxxxxxxxxx4.dkr.ecr.us-east-1.amazonaws.com/dev-scrb-process:v1 (which is what I was expecting? Why is the function name and another identifier prefix included in the image tag?

Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

1. OS: MacOS
2. SAM CLI, version 1.16.0
3. AWS region: us-east-1

[jfuss]

@xirkus No worries. They are slightly related but one is for the SAM Spec vs the CLI.

In regards to your issue, this behavior is by design. When we upload to ECR, we add extra data to all different functions to be in the same ECR repo. We also add part of the sha (the “other identifier”) to the tag to allow redeployment on Lambda. Otherwise the image is the “same” and Lambda will not get updates.

Closing as this is by design.

[EvgeniGordeev]

@jfuss Are there plans to give more control over the tag creation to end users? e.g. if one deploys the same code to 5 different environments why to create 5 different images in ECR.