Unable to connect to docker host from within a container about for-win HOT 12 CLOSED

Hi @toddlucas I was able to confirm that this feature has been added in the latest Edge channel build.
Two DNS entries were created - each for their respective OS
docker.for.mac.localhost
docker.for.win.localhost

I ran a few quick tests and was able to telnet to docker.for.win.localhost from inside a container.

Thanks!
Jason

from for-win.

Hi,

I've was able to connect doing a working arround with ngix by starting it with the following config

stream {
    server {
        listen 10.0.75.1:2375;
        proxy_pass 127.0.0.1:2375;
    }
}

Then, on container I just set DOCKER_HOST variable to 10.0.75.1.

NOTE: My Docker toolbox internal virtual switch subnet address is set to 10.0.75.0 (default), that's why I've used 10.0.75.1 IP address

from for-win.

Hi @toddlucas thank you for reporting this issue. Your use case is common to a lot of users and we are currently trying to find the best way to solve it. However I don't know if/when this will happen yet.

from for-win.

Any update on this issue?
@ecsousa : I tried the workaround with the nginx proxy, but could not get that working (nginx would not bind to the specified ip). Is it possible to post your complete nginx config and your docker(-compose) file?

from for-win.

@vandammeb Here's my nginx config file.

nginx.conf.txt

Note that, if you have changed the subnet address on network config, you will have to change the listen address on nginx config.

Also, remember to specify -e DOCKER_HOST=10.0.75.1 (or your host IP) when you are creating your container, to make sure docker client will try to connect to correct server

I am using the following PowerShell command to find out the correct IP address when creating my container. It should return you the right IP address you should use to replace 10.0.75.1 (on both container creation command line, and nginx file):

(Get-NetIPAddress -AddressFamily IPv4 -InterfaceIndex (Get-NetAdapter | ? {$_.Name -like '*(DockerNAT)*' }).InterfaceIndex).IPAddress

from for-win.

@ecsousa Still no luck with the workaround you suggested. The same nginx bind issue persists:

nginx_1 | 2016/10/10 16:41:17 [emerg] 1#1: bind() to 10.0.75.1:9003 failed (99: Cannot assign requested address)

Would you mind having a look at my stackoverflow question?
My docker-compose file and network info are available there.

from for-win.

@dgageot Any chance this issues has been addressed in the current beta? (i'm using the stable version)

from for-win.

closing this one - it has been resolved in https://github.com/docker/pinata/issues/4026

from for-win.

Hi @jasonbivins , I'm not able to see this repo or issue. Can you give us more details on when and where we might see this fix? Thanks!

from for-win.

Hi @toddlucas Apologies, but that is actually our internal repo

The issue is listed as fixed in 17.06 but I don't see a specific item for it in the release notes. I'll reopen this issue until I can confirm for sure that this was included.

from for-win.

Hi @jasonbivins , thanks for following up. That's great news. Feel free to close.

from for-win.

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

from for-win.