This message was deleted.

so really seems like a lot fo folks are having CA issues. @fast-garage-66093 did something change from copying the CAs into the Distro/VM or fetch implementation? I personally haven't had any issues on 15.1, but seems like there have been a mess of folks with self-signed issues which I assume is a MITM proxy w TLS interception. If they were missing their internal CA in window credmgr/keychain i would expect they would have a ton more issues. And that one i thought was a host side call but node fetch should use schannel on windows and that looks like an openssl error

https://github.com/rancher-sandbox/rancher-desktop/issues/5165#issuecomment-2269584939 we are noticing the same thing. i was able to confirm the certs were in our keychain

How to fix this

It's been a while since I ran anything on Windows... No idea about the first screenshot... But from what I am seeing on the second screenshot: maybe try opening your windows command prompt as administrator? To do this, if my memory serves me correctly: right click on the terminal app and select "Run As Administrator". I can not remember if this option is available by default or if you need to do something to enable it. Someone on Google knows 🙂

I haven't had time to look at this yet, but the error message is confusing. There should be no need to run the

docker

command from an elevated prompt, it normally works just fine from the regular terminal.

yup that error is a curl or fetch operation having a TLS issue. No indication its a permissions thing. Why CA's in the respective OS stores are not being respected is the part i am scratching my head on.

Can you please tell how to fix this @wide-mechanic-33041

no if i knew how to fix it I would have provided the answer.

Okay thanks