Yep, Docker staff is aware of the situation. Please have a look at these threads for more information:
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 …
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-…
Hi,
I created a new docker network like this:
docker network create --subnet 203.0.113.0/24 --gateway 203.0.113.254 iptastic
Then started a new container and assigned it to the new network with a fixed IP address like this:
docker run --net iptastic --ip 203.0.113.2 -d -P --name test_sshd eg_sshd
With regards to IP routing to the new container from my Mac OS, what interface is used by Docker for Mac for this ?
(Crazy spam filter preventing me from posting this because it is too similar. Why yes! It is similar, I am answering a question about the same underlying issue!)
1 Like