-
Notifications
You must be signed in to change notification settings - Fork 230
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
Authentication to Azure ACR fails using admin user #79
Comments
I can take a look tomorrow
|
@jessfraz we talked about this a while back :) - I didn't have a chance to look that far but I'm assuming it requires upstream changes to the auth code. I don't think they're compatible with ACR right now because of differences in the registry protocol. I think GCR had some issues before too, saw several of those folks making PRs a while back. |
It's a server-side isuse. Opne Azure/acr#104 to track it. |
A related issue containerd/containerd#2385 which also blocks image push to ACR. |
any workaround? |
awesome!
…On Wed, Jun 6, 2018 at 4:42 PM Bin Du ***@***.***> wrote:
@aminebizid <https://github.com/aminebizid> ***@***.***
<northtyphoon@2da858c>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#79 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABYNbDXFhi5dMoZPfq3315n7ClP6knwYks5t6FrcgaJpZM4TEkt9>
.
--
Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3
pgp.mit.edu <http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3>
|
Great I’ll start working on VSTS ext. |
opened one unified issue for this :) #128 |
@jessfraz We started to rollout the fix to ACR for Azure/acr#104. Meanwhile can you help integrate one upstream fix to img from containerd/containerd#2386? |
ah i can update the vendor dope! |
Using built binaries for version v0.3.0,
img login
would succeed but any following operation (pull, push, etc) fails with the following error.snapshotting the image failed: failed to fetch oauth token: unexpected status: 400 Bad Request
I was facing a similar issue using skopeo and found that the issue is with the upstream 'containers/image' dependency. see anchore/anchore-engine#18 for details.
Is it possible that the issue with img is related? anyone else having the same issue with Azure ACR?
The text was updated successfully, but these errors were encountered: