Conversation
akash1810
force-pushed
the
aa/cq-docker
branch
from
4492fcd to
8ecf341
Compare
It appears v6.15.0 of the CloudQuery CLI image no longer includes `ca-certificates`, which provides the `update-ca-certificates` command. Add it back!
akash1810
force-pushed
the
aa/cq-docker
branch
from
8ecf341 to
5a44ff0
Compare
This file contains hidden or 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
2 participants
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.
What does this change?
It appears v6.15.0 of the CloudQuery CLI image no longer includes
ca-certificates, which provides theupdate-ca-certificatescommand. Add it back!The changes in #1405 didn't actually do anything as we have to manually publish a new image. I've added a note about this as an inline comment. We should automate this process in future though.
How has it been verified?
I've manually run the workflow to publish an image.