Closed tony-kerz closed 8 years ago
Hi @tony-kerz,
I just bumped into this one the other day too. It seems that currently there is no way to route traffic to container IPs when using the docker-4-mac unfortunately. I have switched back to docker-machine for the time being. See this forum thread: https://forums.docker.com/t/ip-routing-to-container/8424/5
roger that adam, i'll use docker-machine for now as well. u can decide whether to leave this issue open as a placeholder until the docker team decides how to remedy.
Let’s keep it open and I’ll check what’s going on with docker-4-mac regularly. I’d like to see this one working asap, it was a disappointment having to go back to docker-machine…
On 19 May 2016, at 16:46, tony kerz notifications@github.com wrote:
roger that adam, i'll use docker-machine for now as well. u can decide whether to leave this issue open as a placeholder until the docker team decides how to remedy.
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/ContainerSolutions/minimesos/issues/441#issuecomment-220346746
Closing. Blocks on https://github.com/ContainerSolutions/minimesos/issues/431 because of a limitation on docker-java.
running docker for mac:
minimesos up
looks good:looks like docker images are running:
should i be able to ping the master for instance:
i see this issue around docker-4-mac, but it seems to be focused on builds. would this issue prevent from just running under docker-4-mac as well?
any guidance appreciated!