Closed shichimitogarashi closed 7 years ago
Thanks for your report.
I suspect when the proxy turns on and off, it modifies the system proxy settings in some way. By default if the proxy settings change then Docker will restart because it needs to reset the http_proxy
environment variables in the VM.
There is a new "transparent proxy" in 17.07 and later (i.e. in the "edge" channel). If you install edge then you can switch the proxy on with the following commands:
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
In this mode there is no rewriting of environment variables and therefore no need to reboot the VM. Hopefully it will become default in a later version.
It would be nice if there was an option in the menu to just "Don't use a proxy".
@marconett The edge version of Docker For Mac has that option:
It seems like setting Manual Proxy configuration and leaving all fields empty also disables proxy.
oh. weird, it says "Docker 17.09.0-ce-mac34 is currently the newest version available." and it says "This is an edge version." in the preference menu.
thanks for the input!
Same problem when i change Surge's config.
I'm config proxies to Manual proxy configuration
to solve it.
You don't need to setup any proxy setting in below field.
I can confirm that on OSX, using the manual proxy configuration and leaving the fields blank solves the issue. I can toggle the Charles proxy setting on and off without issue now.
Looks good to me as well. Thanks.
I concur with the remarks made by Djs on September 8, 2017 with the additional following remarks: You might want to consider the option of using the edge version of Docker for Mac in configuring proxies to pull images, and to manually have more control over those settings.
Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked
Expected behavior
Docker continues as normal when starting or stopping Charles proxy (https://www.charlesproxy.com/)
Actual behavior
Docker restarts whenever I start or stop the proxy. This is new behavior with 17.06.2-ce-mac27 (19124); previous versions had no problems with this.
(there also appear to be networking problems in containers when running Charles proxy, but if I can get enough information about this, I'll file a separate issue. This is also new)
Information
Docker for Mac: version: 17.06.2-ce-mac27 (4cdec4294a50b2233146b09469b49937dabdebdd) macOS: version 10.12.6 (build: 16G29) logs: /tmp/317ED9B7-865A-4358-8FFE-A98515BA7AF9/20170907-163011.tar.gz [OK] db.git [OK] vmnetd [OK] dns [OK] driver.amd64-linux [OK] virtualization VT-X [OK] app [OK] moby [OK] system [OK] moby-syslog [OK] db [OK] env [OK] virtualization kern.hv_support [OK] slirp [OK] osxfs [OK] moby-console [OK] logs [OK] docker-cli [OK] menubar [OK] disk
Steps to reproduce the behavior
I haven't tried using other local proxies to see if this repros with those as well.