Store proxy CA in the shared Compose volume - #485
Merged
Conversation
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
1 participant
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.
The proxy image starts with HOME=/root, but Compose mounts its CA volume at /home/mitmproxy/.mitmproxy. The CA is written outside the shared volume, so Drukbox rejects sandbox creation with secret entries because its public certificate is missing.
Set the proxy HOME to the mounted directory. Applied the same setting in the production override and preserved the existing CA. Verified Compose configuration, matching public CA fingerprints in the proxy and Drukbox, and a real sandbox request with placeholder substitution, TLS trust, and reattachment. No tests added or run locally.
Fixes DRU-497.