vm: add /etc/ssl/certs as certs copy target #484
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I run colima behind a corporate VPN.
I was running into
x509 certificate signed by unknown authorityissues and stumbled into this helpful issue. I followed the instructions here and the problem did not resolve until I manually copied the cert from/etc/docker/certs.dto/etc/ssl/certswithin the VM! This is just a guess, but maybe it's because I'm using containerd instead of docker as the container runtime.Either way, having to ssh into the VM and manually copy a file doesn't seem like a scalable solution, which is why I'm submitting this PR. Completely amenable to feedback. Thank you for the amazing work you do. I ❤️ Colima.