Need to specify proxy settings

foolusion · May 20, 2016, 8:48pm

I used to be able to set the proxy for Docker beta for mac using the following script.

function dockerproxyon {
  screen -L -dmS docker ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty
  screen -p 0 -X stuff $(echo -ne '\015')$(echo -ne '\015')$(echo -ne '\015')
  sleep 1
  echo "logging in"
  screen -S docker -p 0 -X stuff root
  screen -S docker -p 0 -X stuff $(echo -ne '\015')
  sleep 2
  echo "stripping old proxy config"
  screen -S docker -p 0 -X stuff "sed -i -E '/_proxy/d' /etc/init.d/docker"$(echo -ne '\015')
  sleep 1
  echo "Setting proxy in docker."
  screen -S docker -p 0 -X stuff "sed -i -E '/Starting Docker/ a export no_proxy=*internal.net' /etc/init.d/docker"$(echo -ne '\015')
  screen -S docker -p 0 -X stuff "sed -i -E '/Starting Docker/ a export https_proxy=http://myproxy:3128' /etc/init.d/docker"$(echo -ne '\015')
  screen -S docker -p 0 -X stuff "sed -i -E '/Starting Docker/ a export http_proxy=http://myproxy:3128' /etc/init.d/docker"$(echo -ne '\015')
  
  echo "restarting docker service"
  screen -S docker -p 0 -X stuff "service docker restart"$(echo -ne '\015')
  screen -S docker -p 0 -X stuff "service docker restart"$(echo -ne '\015')
  screen -S docker -p 0 -X stuff "exit"$(echo -ne '\015')
  screen -S docker -X stuff quit
}

but now i can not restart the docker service in verion Version 1.11.1-beta12 (build: 7528)
4151b0fc71e51fb8e551d0a1870893ac99a379bc

foolusion · May 20, 2016, 9:09pm

Rolling back to Version 1.11.1-beta11 (build: 6974)
37559e5f6acd56a4810963acc7001e88f2d88017 fixed my issue.

theothermattm · May 23, 2016, 5:16pm

+1 unfortunately beta is unusable til this is available. can’t seem to get any of the workarounds working either.

davetucker · May 27, 2016, 9:44am

Good news! We now have support for reading HTTP Proxy settings from OSX.
Please update to Beta 13 and let us know how you get on!

flaccid · May 27, 2016, 9:49am

@davetucker might be useful if the Settings in GUI has some kind of hint that it uses the System Preferences config for proxy (https://beta.docker.com/docs/mac/networking/).

maltebreuer · May 27, 2016, 9:56am

@davetucker Works as expected. Just tested it with Beta 13.

swepawe · May 28, 2016, 2:16pm

Just OS X or Windows too?
edit: Fix for Windows is still work in progress: #13144

theothermattm · May 27, 2016, 12:26pm

Thanks for responding so quickly with this feature! This still didn’t work for me.

Here’s some output from attaching to the docker VM via screen right after starting up docker for mac:

`
moby:~# curl http://google.com
curl: (7) Failed to connect to google.com port 80: Connection refused
moby:~# export http_proxy=http://myproxy.mycompany.com:80
moby:~# export https_proxy=$http_proxy
moby:~# curl http://google.com

301 Moved

The document has moved here. `

davetucker · May 27, 2016, 9:46pm

Are you definitely running Beta 13? If you have your proxy config completed in System Preferences, this should automatically appear inside Moby. Also, you may want to try with curl -L to follow redirects.

databus23 · May 30, 2016, 3:22pm

I tried this and I’m seeing two problems with this

My company relies on Proxy auto-configuration (PAC) for correctly setting the proxy and defining exclusions. This obviously is not picked up by Docker for Mac. If I set an http_proxy explicitly in the system settings I loose the PAC configuration and have to define exclusions manually.
The no_proxy environment value is copied unchanged from the system settings. On OSX its possible to define exclusions with ‘*’ as the wildcard character (e.g. *.my-company.com). There is almost no Linux/Unix software that understands this format including golang. On Linux/Unix its common that the no_proxy environment variable just contains a list of hostnames suffixes (e.g. my-company.com). So to make the no_proxy environment variable work for docker the no_proxy settings from OSX should be stripped from *. and CIDR notations and if your at it your best remove spaces from the value entirely because some linux software trips over that as well.

Both problems could be mitigated by providing explicit configuration settings in the Docker.app settings as suggested by a previous post.

berkgokden · May 31, 2016, 8:09am

I have the same problem here. I have PAC configuration. When I set http proxy directly, other applications have problems.

davetucker · May 31, 2016, 10:30am

Thanks for the feedback. Re: PAC, this is unfortunate
I’ve opened issue (#3516) on our tracker to add support for this.
Re: no_proxy formatting, this has also been reported in this post, we’re working on a fix - issue (#3514)

As for providing UI for setting proxy configuration… I’ve opened an issue for that too. Ideally it will display the values that have been auto-detected and allow you to override them.

theothermattm · May 31, 2016, 12:30pm

Yes, I’m definitely running beta 13. After seeing @databus23’s comment, I realized that I am also on a PAC configuration which is why it isn’t working.

databus23 · May 31, 2016, 1:16pm

This tracker is not public by any chance?

This post is only concerned about whitespace. Could you also add the adjustment of wildcard notations to the mix so that it is in a format that unix tools understand it?

davetucker · May 31, 2016, 1:53pm

No the tracker isn’t public, but the issue numbers will appear as fixed in the changelog.
The adjustment of wildcards is tracked in (#3535)

hiucimon · June 2, 2016, 2:16pm

I also use auto proxy settings on our corporate network, and when I try to run:

$ docker run hello-world
Unable to find image ‘hello-world:latest’ locally
Pulling repository docker.io/library/hello-world
docker: Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/hello-world/images. You may want to check your internet connection or if you are behind a proxy…
See ‘docker run --help’.

When I manually set the proxy information, INCLUDING the login information, I get:
$ docker run hello-world
Unable to find image ‘hello-world:latest’ locally
Pulling repository docker.io/library/hello-world
docker: Error while pulling image: Get https://index.docker.io/v1/repositories/library/hello-world/images: Proxy Authentication Required.
See ‘docker run --help’.

emmanueltsouris · June 7, 2016, 7:16pm

+1 from me as well, the auto-proxy config seems to complicate things. A setting allowing us to just set the proxy in the VM seems like a good fix.

jlamillan · June 7, 2016, 8:49pm

Setting the proxy at the system preferences is a decent workaround, but poses an issue in that the change affects every app on the system that uses the connection. This can lead to unexpected connection problems when a client isn’t explicitly going through the OS level proxy, which is why we much prefer the previous method of setting the proxy on the Docker daemon itself and letting the user set proxy settings other clients themselves.

pholbrook · June 13, 2016, 3:34pm

My company implements Man In the Middle sniffing of all HTTPS connections, so I’m getting this error when I try to pull using beta 15:

$ docker pull fedora:latest
Pulling repository docker.io/library/fedora
Error while pulling image: Get https://index.docker.io/v1/repositories/library/fedora/images: x509: certificate signed by unknown authority

I need a way to be able to install our official corporate MITM certificate.

flaccid · June 16, 2016, 2:11am

Not sure what happened. With Version 1.11.2-beta15 (build: 9168) it appears as though proxy support is no longer working for me.

$ docker pull busybox
Using default tag: latest
Pulling repository docker.io/library/busybox
Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/busybox/images. You may want to check your internet connection or if you are behind a proxy.

How can this be debugged and the VM checked for settings etc.?