-
Notifications
You must be signed in to change notification settings - Fork 36
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
Login problem with Private Registry #314
Comments
we should be using the credentials from the |
Even through i am definitely logged in, when i try to login again i get:
And on publish the same error. |
Had some time to look into and debug the code and found that TryParseAuthenticationInfo returns always false for my registry.
to this:
the image is pushed to the registry. |
Ok, so what I'm understanding here is that there is some kind of conventional default for the |
I think the problem is that realm is not always necessary a url. Mozilla here has the following example for basic authentication
Also the registry, by default, does not return any service header in the response and so the For a test setup you can run the command above but without the 3 lines for the certificates. Then on the client enable the insecure registry in docker daemon.json for mac or linux or in the desktop engine setting for windows. |
This is great - it should be relatively easy to capture this in a test thread and then make this change. I appreciate all the investigation you've done here! |
Worth noting as well that the call to GetAuthenticationAsync only passes in the If the private registry is running on a non-standard port (e.g. 5000 as is used in Docker's own examples when using the Maybe the call to |
Great call-out - I think we've surfaced this concept elsewhere in the code as the RegistryName, which should also be used to find the authentication information. |
Hi @baronfel , any update on this issue? I'm also having troubles publishing containers. However, in my case I can adjust the www-authenticate header. These values don't work. Thanks |
Will this issue be fixed before code freeze on this repo? Thanks |
Hey @avber sadly we won't be able to get to this before the code freeze, but we do want to spend the next iteration knocking down bugs like this. |
Hi @baronfel , Thanks for the info. What values should I put into the www-authenticate header (see above) to make the current implementation work? |
Assigned this one to me because I have a PR out for it that is almost ready. |
This should be fixed in .NET 8. |
Having problem pushing to private registry.
Using 7.0.200-preview.22628.1
The text was updated successfully, but these errors were encountered: