+1 This is the only issue right now preventing me from going any further with the beta app. I’m sticking with Virtualbox and boot2docker until this is reasonably resolved. With boot2docker, doing a run --add-host=dh:10.0.2.2 gives me access from a container outside to the host and any port on the host. I haven’t yet found any IPv4 address within the container that will provide that like boot2docker/toobox/… I’ve read tons of comments and tried docker0, docker.local, utun0, localhost, --net host, network=hostnet/nat, docker-ipv4, host-ipv4, bridge100, with/without --add-host and probably others.
mitack
(Mitack)
3
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Should docker run --net=host work? | 30 | 278582 | October 17, 2021 | |
| Accessing host machine from within docker container | 30 | 669456 | June 10, 2021 | |
| Support tap interface for direct container access (incl. multi-host) | 27 | 26842 | October 17, 2023 | |
| Explain networking known limitations, explain "host" | 12 | 14695 | July 20, 2023 | |
| Confused about networking defaults, how to get VM IP with native port forwarding off? | 15 | 6433 | September 28, 2016 |