Repository navigation
chore: configure devcontainer proxy and host networking - #98
Merged
Merged
Conversation
Add remaining SSL/CA env vars for uv and use --network=host for build and runtime so the WSL2 loopback-forwarded corporate proxy is reachable from inside the container (fixes github-cli feature install failure). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This branch was previously deployed
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.
Summary
SSL_CERT_DIR,PIP_CERT) so pip/curl/etc. trust the injected cert during buildTest plan
pip install,curl, andnpm/yarninside the container succeed