Outdated documentation for Experimental Transparent Proxy Feature
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker
- Domain
- documentation, networking
Research direction
Start with the transparent HTTP proxy documentation at moby/vpnkit/docs/transparent-http-proxy.md and review the referenced Docker for Mac 7.12 issue about the deprecated database folder. Reproduce the listed macOS proxy steps if the environment is available, then determine whether the feature and instructions are still supported. Done means the documentation accurately describes current setup or clearly marks the feature as unavailable.
Written by the indexing model from the issue text.
Description
I am having issues enabling the experimental Transparent proxy feature. The documentation states these instructions to this feature:
cd ~/Library/Containers/com.docker.docker/Data/database/
git reset --hard
mkdir -p com.docker.driver.amd64-linux/slirp
echo -n true > com.docker.driver.amd64-linux/slirp/enable-http-intercept
git add com.docker.driver.amd64-linux/slirp/enable-http-intercept
git commit -s -m 'Enable HTTP interception'
However it appears the "database" folder has been deprecated since version 7.12. I have tried adding the folders/configurations listed in the above instructions myself but have had no luck with getting containers to take my host machine's system configurations.
Does this mean this feature has also been deprecated? This is a really amazing feature that would save my team a great deal of proxy configurations since we work behind a corporate proxy.
Steps to Reproduce:
- Follow "Enabling the proxy in recent Docker for Mac builds" instructions: https://github.com/moby/vpnkit/blob/master/docs/transparent-http-proxy.md
- Set system proxy on host machine to corporate or local proxy for testing(set system proxy setting to point to mitmproxy so you can monitor outgoing traffic)
- Startup centos container
docker run -it --rm centos - Run
curl www.google.comfrom within container, which returns result "curl: (6) Could not resolve host: www.google.com." Notice mitmproxy did not pickup the call to http://www.google.com
System: macOS High Sierra Version 10.13.6
Docker for Mac CE Edge: Engine 18.09.0
- Dominant language
- OCaml
- Stars
- 1.2k
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from moby/vpnkit
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
mozilla/bedrock#17413 · 1 reaction ·
Maintainers usually reply within 2 days
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
github/copilot-sdk#2804 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
drizzle-team/drizzle-orm#6418 ·
Maintainers usually reply within 4 days
-
automated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lirantal/discoprint#31 ·
Maintainers usually reply within 1 day