Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error connecting to ECR with temporary password #3202

Closed
macsj200 opened this issue Sep 10, 2021 · 2 comments
Closed

Error connecting to ECR with temporary password #3202

macsj200 opened this issue Sep 10, 2021 · 2 comments

Comments

@macsj200
Copy link

I'm trying to connect to AWS ECR via the registries tab using the username AWS and a temporary password.

I obtain the temporary password with aws ecr get-login-password.

When I connect to the registry I get an Invalid JSON error.
image

Additionally, I encounter the following errors with incorrect/missing credentials:

Stale temporary password 403 error

image

No username/password set error

image

Does anybody have any suggestions for how to connect to ECR via this extension?

Note that I was able to successfully push a tagged image to ECR via the docker CLI so I believe my credentials are functional.

Related issue: I'd like to be able to easily re-authenticate (specify a new password) with an ECR URI.

This issue is also related, but I'd like to try this without re-configuring something like credsStore in ~/.docker/config.json (I already tried using the ECR creds helper and I want to see if I can get it to work with password-based auth).

@macsj200
Copy link
Author

@bwateratmsft
Copy link
Collaborator

The initial issue, about unexpected end of JSON input, would be a dupe of #3185 and should be fixed in the upcoming 1.17 release.

ECR may work with the temp password (once the fix for #3185 is in place), as it is a V2 compliant registry, but Amazon has their own mechanism for "real" authentication (i.e. not the temp password). Consequently, an auth mechanism would have to be implemented for ECR to work properly. That is covered between #869 and #2033.

@microsoft microsoft locked and limited conversation to collaborators Oct 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants