Cannot access app by container IP

[codenvy (Andrii Parfonov)]

I can see the app on localhost. But I need to access it by IP as well. I have read similar threads but all in vain.

docker inspect shows 172.17.0.2. Why can’t I see my app when I go to that IP? Why is it just localhost?

Also, how can I get the VM IP?

[richt (Richard Tong)]

I just had the same issue. It looks like there is automatic mapping happening in docker for mac. So if you do a -v 3000:3000 for instance then automatically this port gets mapped to Mac port 3000, but the behavior seems unreliable. I’ve been trying to use node-inspector on port 8080 and it has worked once but then fails.

[aleveille (Alexandre)]

You might want to look into these threads:

Network bridge on host

After reading all the related forum threads, i still don’t get it: do docker mac beta is supposed to set a docker0 bridge interface on the osx host, like it does on linux, so that containers are directly available from host via their local network ip ? Or this bridge is only set/available on the alpine vm itself ? Information $ pinata diagnose -u OS X: version 10.11.4 (build: 15E65) Docker.app: version v1.11.1-beta11 Running diagnostic tests: [OK] docker-cli [OK] Moby booted [OK] driver.amd64-…

Host excluded from bridge network

Expected behavior Host should be able to access the containers by their IP addresses. Actual behavior On a bridge network setup I am not able do any operations using the container’s IP addresses. Information On v1.11.1-beta11 I cant access any of the containers from the host by using their IP addresses. I can execute commands and get into the boxes by running bash through docker exec but whenever I try to access the containers by their IP addresses those operations will fail. Essentially I’m …

IP address given to container is not routable in bridge mode

Expected behavior When launching a container which has HostConfig.NetworkMode=default (which ends up using the bridged network), I can connect to exposed ports via the container’s IP address. Actual behavior The container appears to be using the bridged network but the IP address cannot be connected to from the host. "NetworkSettings": { "Bridge": "", "SandboxID": "f0638e5bd88c370e6128bde1b35b173cb96d7644fb2719e2bd02785a6f197fbd", "HairpinMode": fals…

[mickaelbaron]

@Andrii Parfonov, do you solve your problem ? I’ve the same problem. I tested on a Linux distribution and it’s working.

On Docker4Mac (1.12.2) i can’t use any container by IP.

Mickael

[cbrunnkvist (Conny Brunnkvist)]

I thought I had this problem: the docs don’t say exactly clearly what will happen when switching from docker-machine/vbox (of Docker Toolbox) to D. for Mac and basically no network access was working, automatic or -p explicit, container IP (found only via network inspect or host IP.

I eventually realized that run parameters must come before, not after, the image name. doh Then forwarding turned out to be working just fine.

Not sure but that might be something that has changed in recent versions.

[wovo]

So you should be able to access containers from your container host using the container IP . You can use docker inspect <container ID> to get your container’s IP address.

Does that answer your question?