-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Machine create fails behind proxy #78
Comments
Once i restart the shell,
|
@vraman0601 Thanks for reporting. There are known issues with the Toolbox on proxy / corporate VPNs. We are looking into this issue. Thanks! |
I do not think the install issue is because of some thing to do with the proxy... The installer failure log below: Aug 14 10:11:00 M00973492.nordstrom.net installd[1541]: PackageKit: allow user idle system sleep |
The same problem on my mac:
some err log:
|
I got same issue. But docker still running fine after click And the installation issue is happen only when behind proxy. Here is my question, i can |
Edit startup.sh.
|
Got it to work on my 2009 MacBook Pro, but the installer failed with this message on my 2015 Yosemite MacBook Air. No proxies involved. |
I disabled http proxy, and this problem resolved. |
Had to unset the proxy, if it just listened to $no_proxy it would already be sufficient for me since i only use environment settings to control proxy's. |
See #102 for some tips. Investigating a better solution |
+1 |
1 similar comment
+1 |
@JeffDM I was looking to see if I could contribute to this. It feels like toolbox is based on electron, but this repo doesn't seem to have the actual source files. The contributing instructions just say to download the toolbox from the website. Am I missing something, or is the source for toolbox not yet out there for contribution? |
+1 |
see also docker/kitematic#1031 (comment) |
+1 |
I am trying to work with docker-machine behind a proxy and I was running into this issue. I could not get Docker to work on my host machine. And I realized it was due to the fact that the NO_PROXY environment variable was not being set by using eval "$(docker-machine env default)" Hope this helps. |
Thanks @FugDev. Linking FugDev's temp potential solution here. On windows my solution is following:
|
As I confirmed in another ticket #102 before, update directly in boot2docker with file of So above steps still need be reviewed. I currently think to adjust Will update if this is helpful or not. |
With latest toolbox version v1.9.0, I can set proxy in Second, when I install docker toolbox v1.9.0 behind proxy, there is no problem, it is installed smoothly. Seems the problem has been fixed. I also updated ticket #102 as well with the detail steps on how to work with proxy and no proxy in same docker machine. |
I disabled http proxy, and this problem resolved. |
If anyone still has problems with this on Mac or Windows 10+, please contact me at mchiang@docker.com. We are working on something to help address this issue. |
I had a problem with docker terminal. I cannot able to connect with docker hub and it shows a problem with docker cache files and machine files. |
Hello, I installed docker on windows 7. I cannot get it to run hello-world. Since I am behind a firewall I tried docker-machine ssh default |
@Loganguy Did you try setting NO_PROXY to your "156..." ip address? Thats the only tip I would have given you didn't mention it above. |
Hello,
The Installation of toolbox fails on mac (behind a proxy).
I actually see the apps installed,
![image](https://cloud.githubusercontent.com/assets/7082789/9255409/edef3a90-419d-11e5-82df-15bacd6f968e.png)
when i run the docker command,
It was the same issue on toolbox 1.8.0
docker/kitematic#914
Complete Log on first run:
bash
. '/Applications/Docker/Docker Quickstart Terminal.app/Contents/Resources/Scripts/start.sh'
Last login: Thu Aug 13 09:04:08 on ttys000
x3it:
$bash$. '/Applications/Docker/Docker Quickstart Terminal.app/Contents/Resources/Scripts/start.sh'x3it:
Creating Machine default...
Creating CA: /Users/x3it/.docker/machine/certs/ca.pem
Creating client certificate: /Users/x3it/.docker/machine/certs/cert.pem
executing: /usr/local/bin/VBoxManage
STDOUT: Oracle VM VirtualBox Command Line Management Interface Version 5.0.0
(C) 2005-2015 Oracle Corporation
All rights reserved.
< ... clipped ... >
Using SSH client type: external
About to run SSH command:
sudo /etc/init.d/docker start
&{/usr/bin/ssh [/usr/bin/ssh -o PasswordAuthentication=no -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -i /Users/x3it/.docker/machine/machines/default/id_rsa -p 51441 docker@localhost sudo /etc/init.d/docker start] [] [] false [] [] [] [] }
SSH cmd err, output: : Need TLS certs for default,127.0.0.1,10.0.2.15,192.168.99.100
Generate server cert
/usr/local/bin/generate_cert --host=default,127.0.0.1,10.0.2.15,192.168.99.100 --ca=/var/lib/boot2docker/ca.pem --ca-key=/var/lib/boot2docker/tls/cakey.pem --cert=/var/lib/boot2docker/server.pem --key=/var/lib/boot2docker/server-key.pem --org=Boot2Docker
2015/08/13 16:31:53 Preventing overwrite: the following files already exist: "/var/lib/boot2docker/server.pem" "/var/lib/boot2docker/server-key.pem". To overwrite files, add
--overwrite
.Daemon not responding yet: dial tcp 192.168.99.100:2376: connection refused
To see how to connect Docker to this machine, run: docker-machine env default
Starting machine default...
Started machines may have new IP addresses. You may need to re-run the
docker-machine env
command.Setting environment variables for machine default...
docker is configured to use the default machine with IP 192.168.99.100
For help getting started, check out the docs at https://docs.docker.com
x3it:~$
x3it:
$docker run ubuntu echo "hi"$An error occurred trying to connect: Post https://192.168.99.100:2376/v1.20/containers/create: Forbidden
x3it:
The text was updated successfully, but these errors were encountered: