-
Notifications
You must be signed in to change notification settings - Fork 181
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
ORAS CLI should support interacting with docker.io #542
Comments
The root cause is the However, when accessing the credentials, the hostname @junczhu Could you help fixing this bug and update internal/credential/store.go to match the same behavior as docker daemon and docker CLI? |
Thanks for the insight. |
PR #549 is opened for this fix. /cc @qweeah @shizhMSFT |
For your information: By default, command And when using docker cli to push an image to the docker hub, with default hostname, only the credential on line 3 can be used. When explicitly using registry-1.docker.io as hostname, like In ORAS, we have mapped |
Hi @FeynmanZhou , the issue has been fixed. /cc @shizhMSFT @qweeah |
@junczhu Thanks for your quick response and action. I will test it from the latest main branch. Let's keep this issue open until I verify this issue. |
@shizhMSFT @junczhu |
Currently, ORAS is not able to authenticate
docker.io
and will return 401 error:It requires users to specify
registry-1.docker.io
to authenticate with DockerHub. I think ORAS should support the most common domaindocker.io
when interacting with DockerHub.The text was updated successfully, but these errors were encountered: