What additional configuration is needed to run the initial Build your first .NET Aspire solution tutorial using Podman?

[jcbeck37]

I'm following the steps, utilizing the .NET Aspire Starter App template. I have Podman running on my Windows 11 machine.

When I run the app, the "cache" project fails to start.

Here's the console message:

Error: internal error: unable to copy from source docker://redis:7.4: initializing source docker://redis:7.4: pinging container registry registry-1.docker.io: Get "https://registry-1.docker.io/v2/": tls: failed to verify certificate: x509: certificate signed by unknown authority

[danegsta]

Internally, Aspire simply uses the Podman (or Docker) CLI to run any container specific commands, so Podman should just work if you can run commands successfully yourself (i.e. if podman image pull redis:7.4 works, Aspire should work as well). If you're getting a TLS certificate error while trying to pull or run an image, I'd check to see if you have a proxy on your machine that could be interfering with the request.

[jcbeck37]

Yes - part of an organization that has my machine behind a proxy. Wonder if I can still use Aspire with containerization with a workaround or just have to pursue other solutions. Thanks for the help.

[danegsta]

Any time a proxy is intercepting and modifying https traffic it complicates things as that’s effectively a man-in-the-middle scenario, a malicious version of which is one of the things that https/TLS is designed to protect against.

The proxy solution your IT is using likely adds one or more additional trusted certificates to your machine that makes it trust the proxy, but the Podman (or Docker) backend is running in WSL, which runs lightweight VM based Linux distributions. WSL distros are a full Linux OS, which means they have their own certificate trust stores. The certificate that’s being trusted on the host Windows OS would also need to be added to the trust store on any WSL instances for them to also trust the proxy.