Closed smargoli2 closed 3 months ago
Does the issue only happen when pushing the image, or when browsing the existing images on the ACR? We use the CLI to push so I would expect that to be working, but use fetch
for browsing images.
I checked now, I see that I can't browse the existing images either. Same error.
Similar to #4245 but this is definitely due to proxy and not self-signed certs.
@smargoli2 did it work in version 1.28.0 of the Docker extension and break in version 1.29.0?
I don't know, I installed this proxy yesterday. It also has its own certificates...
In VSCode's settings, look for "Http: Proxy Strict SSL". Does disabling that have any effect?
That's already unchecked
Can you tell me what url Docker is using? I can add it to a whitelist
In this case, it would be \<yourregistryname>.azurecr.io. I would whitelist all of azurecr.io.
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
I have a proxy server installed on my PC and I am getting 'fetch failed' when I try to push a container to an azure container registry. I can do it using the cli, but I would like to know if there is a way to make the UI work with my current setup. Can you provide the url that the service is calling so I can add it to the proxy ignore list?