Skip to content
This repository has been archived by the owner on Jun 11, 2021. It is now read-only.

Proxy / VPN error reports #1031

Closed
mchiang0610 opened this issue Sep 12, 2015 · 15 comments
Closed

Proxy / VPN error reports #1031

mchiang0610 opened this issue Sep 12, 2015 · 15 comments

Comments

@mchiang0610
Copy link
Contributor

No description provided.

@FugDev
Copy link

FugDev commented Sep 12, 2015

On windows my solution is following:

create a windows batch script "C:\Program Files\Docker Toolbox\kitematic_proxy.cmd" and insert following script and replace "YOUR_PROXY" with the http://host:port of your proxy
-------------
set proxy=YOUR_PROXY
SET HTTP_PROXY=%proxy%
SET HTTPS_PROXY=%proxy%
for /f %%i in ('docker-machine.exe ip default') do set DOCKER_HOST=%%i
SET NO_PROXY=%DOCKER_HOST%
set DOCKER_HOST=tcp://%DOCKER_HOST%:2376
cd Kitematic
Kitematic.exe
-------------


Btw. if you have generally an enterpise proxy between your station and internet you also shall configure this proxy in your boot2docker vm host:

Because of worng keyboard layout and problems with special key in oracle virtual box native console i connected with WinScp on my docker host using DOCKER_HOST IP login user:docker and pwd:tcuser. Then edit the profile to add proxy settings:
-------------
sudo vi /var/lib/boot2docker/profile

Press 'i' to start editing mode
export HTTP_PROXY=http://your.proxy.name:8080
export HTTPS_PROXY=http://your.proxy.name:8080


Press 'escape' and then type ':x' to save and exit the file. Now retsart your vm to make proxy active

@stritti
Copy link

stritti commented Sep 27, 2015

Thanks @FugDev ! Your cmd-file is workeing for me, too.

@dirkluijk
Copy link

Same issue here. As far as I know, we are not using a corporate proxy (so I don't know a proxy server address), but there is a root certificate "injected" somewhere. I want to mark the certificate as trusted.

image

@Akhena
Copy link

Akhena commented Nov 4, 2015

I am also trying to find a way to make the certificate of our proxy trusted by Kitematic. Maybe in a future release?

@manojsh1984
Copy link

image
getting error any solution

@zivc
Copy link

zivc commented Jan 18, 2016

image

$ env 
HTTPS_PROXY=http://10.244.161.20:3128 
HTTP_PROXY=http://10.244.161.20:3128

@FrenchBen
Copy link
Contributor

@zivc Please see how to properly set this up by following the Wiki info:
https://github.com/docker/kitematic/wiki/Common-Proxy-Issues-&-Fixes

@CrystalQian
Copy link

@Akhena @zivc ,hi,I have meet the same issue with you, how do you solve the problem finally?

@Akhena
Copy link

Akhena commented Jan 28, 2016

@BecauseofLxcCheckpoint Unfortunately (because of this issue) I don't use kitematic anymore in my professional environment

@mchiang0610
Copy link
Contributor Author

We are trying to address this issue with the new Docker for Mac and Windows betas. Please sign up at https://beta.docker.com if you are interested. Ping me at mchiang@docker.com, if you need to a pass. Please mention this issue so I know.

@patdohere
Copy link

+1 that I'm having this issue on OS X

@mchiang0610
Copy link
Contributor Author

@patdohere is this with Docker for Mac beta as well?

@patdohere
Copy link

Yes this is Docker for Mac. Only with Kitematic when I'm behind a VPN.

@FrenchBen
Copy link
Contributor

@patdohere We release Kitematic v0.10.2 today which includes a few fixes. Can you check if that fixed your problem?

@patdohere
Copy link

Seems to be fixed on my end 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

10 participants