Describe the bug
The login hard codes to the ipv4 registry .dkr.ecr.eu-central-1.amazonaws.com, there is no way to login into the ipv6 dual stack endpoint e.g. .dkr-ecr..on.aws
To Reproduce
Steps to reproduce the behavior:
> Run aws-actions/amazon-ecr-login@v2
with:
registries: 1234
mask-password: true
registry-type: private
skip-logout: false
Using environment variable credentials.
Logging into registry 1234.dkr.ecr.eu-central-1.amazonaws.com
It Logins only to amazonaws.com
Expected behavior
also login to .on.aws registry so the docker client recognises the login or allow specifying the registry name
Screenshots
see reprodiuce
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
Describe the bug
The login hard codes to the ipv4 registry .dkr.ecr.eu-central-1.amazonaws.com, there is no way to login into the ipv6 dual stack endpoint e.g. .dkr-ecr..on.aws
To Reproduce
Steps to reproduce the behavior:
It Logins only to amazonaws.com
Expected behavior
also login to .on.aws registry so the docker client recognises the login or allow specifying the registry name
Screenshots
see reprodiuce
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.