on OSX, cannot reach web container by IP

[james-nesbitt]

When starting the compose on OSX, and retrieving the IP for the www container, you cannot reach that container by IP.

The web browser hangs

[james-nesbitt]

This is likely a networking issues only. The containers all start, and they are assigned IPs.

docker-compose starts each application with it's own separate bridge interface, so that containers can't talk across applications. It could be that the MacOSX docker client doesn't manage these custom networks, (only the default docker network)

[aleksijohansson]

It seems that connecting directly to any container IP on Docker for Mac beta doesn't work. Tested with plain nginx image.

[james-nesbitt]

@artursv has had some success. I am going to start a patch based on his recommendations.

[james-nesbitt]

#26 should fix this. Will ask @artursv for comment/advice

[hkirsman]

Didn't work.
Ran with:
wundertools/compose up --build

Used Docker beta: 1.11.0-beta9 (build: 6388)"

[artursv]

Designated IP address didn't work for me either. Forwarded port at 0.0.0.0:8080 did tough.

[james-nesbitt]

It's true, the current effort does not give IP based access, but it does give access.

[aleksijohansson]

Accessing container IP directly is a known issue on the Docker for Mac beta and not actively being solved https://forums.docker.com/t/ip-routing-to-container/8424/5

We can go around this by using this mapping to localhost for now.

[hkirsman]

@aleksijohansson So you mean use localhost:8080 instead of the container ip? But what ip should I use from inside the container to access for example database?