Private registry: Fail to verify first certificate on non-self-signed certificate.

[grhm]

Repro steps:

Create private registry

Create a private registry, with SSL enabled using a certificate issued by an internal/private CA (e.g using mkcert)
Registry works for pushing/pulling images (certificate is trusted)

Exercise issue

In VSCode, right click on Registries\Private Registries in docker explorer.
Choose "Connect to a Private Registry … (Preview)
Enter "https://localhost:5443/"
Press enter to ignore username

Action: vscode-docker.connectCustomRegistry
Error type: RequestError
Error Message: Error: unable to verify the first certificate

Version: 0.3.1
OS: win32

[grhm]

Actually, this looks like it's the same issue as #483.
So closing this as a duplicate.

[grhm]

Yes. Certificate is in the windows cert store.

…

On Fri, 9 Nov 2018, 18:09 Stephen Weatherford (MSFT) < ***@***.*** wrote: Do you have your certificate in the Windows certificate store? Thx. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#613 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAlBylnlBIbTNy6Tw0jVnBKHXmvcbEYhks5utcTPgaJpZM4YW9Op> .

[StephenWeatherford]

This was released a while ago.