Added documentation about using a custom CA with Docker #268
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.
Our company is using custom CA infrastructure, and I faced the problem of either disable tls_verify or somehow use our CA certificates.
We also had newer certificates that were signed by Sectigo, which are included in the default public CA certificates, but not in the Docker image, since it uses something from 2023.
I tried to open a feature request #264, but it was not successful, so I went on figuring out how to do this.
Turns out the suggestions did not work, as the Docker image ignores the bind mounted certificate store, and you also have to set a variable for Python so the exporter actually uses the file.
Since I spent quite much time trying to figure this all out, I thought it will be useful for other people to include my findings in the documentation.