docker: remove cert cache directory before copying host certs #1112
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.
Currently, colima would copy self-signed root CA certs from the
~/.docker.certs.d/
directory to the VM. This allows docker daemon in the VM to pull from registries that are signed with a self-signed cert.However, when removing certs from the
~/.docker/certs.d
directory, they would not be removed from the VM. More confusingly, even after runningcolima delete && colima start
, the same custom certs are still present in the newly created VM.This PR would first delete the intermediate cache directory prior to copying the certs from
~/.docker/certs.d
, which should resolve the certs persistence across colima deletion/creation.Note that certs will still be persisted across colima restart, since they are still present in the VM. While we can simply remove all certs from
/etc/docker/certs.d
, it would be trickier to selectively remove the added certs in/etc/ssl/certs
, and we can probably tackle that in a subsequent PR.