Skip to content
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

Load custom CA certificates from Windows trust store into Podman Machine #3821

Closed
ThomasVitale opened this issue Sep 7, 2023 · 4 comments
Closed

Comments

@ThomasVitale
Copy link

Is your enhancement related to a problem? Please describe

When using Podman Desktop on Windows (WSL2) in an enterprise setup, there can be different services using a private CA (such as container registries or artifact repositories). In order for Podman to trust the certificates, they can be loaded manually into the Podman machine.

Describe the solution you'd like

I would like Podman Desktop to take care of loading the same Windows host trust store into the Podman machine, similar to what Docker Desktop does.

Describe alternatives you've considered

The alternative would be loading the certificates manually after creating a new Podman machine (as documented here) or asking Podman to skip the certificate verification (as documented here).

Additional context

With some guidance, I'd be available to help out with this task.

@axel7083
Copy link
Contributor

I really like this possibility since, installing manually is kinda tedious

@ThomasVitale
Copy link
Author

ThomasVitale commented Sep 26, 2023

One additional problem is that even after loading custom CA certificates manually into the Podman machine, builds from Dockerfiles triggered from the Docker CLI will not work because they use BuildKit by default but the CA certificates are not mounted into the BuildKit container running in Podman. Perhaps that deserves a separate issue after fixing this one (i.e. mounting CA certificates from the Podman machine into the BuildKit container).

Copy link
Contributor

This issue has been automatically marked as stale because it has not had activity in the last 6 months. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions!

Copy link
Contributor

This issue has been automatically closed because it has not had any further activity in the last 30 days. Thank you for your contributions!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants