Docker Community Forums

Share and learn in the Docker community.

Unable to access exposed Weave network from the host machine

docker

(Jens Ulrich Hjuler Pedersen) #1

Expected behavior

That we can access our containers on the weave network, by IP (10.32.0.0/16)
Simple routes and weave expose usually works really great.

Actual behavior

We’re unable to even create the routes that are needed to direct traffic into the VM, and then the Weave network.
Switching the network to nat-mode seems to get us a bit closer to what we want, but it’s not great.

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-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Docker logs are being collected into /tmp/20160511-092157.tar.gz
Most specific failure is: No error was detected
Your unique id is: F91C6360-B688-487E-ACB4-26EBC2C6F851
Please quote this in all correspondence.

Steps to reproduce the behavior

  1. Install Docker for Mac
  2. Install Weave:
    sudo curl -L git.io/weave -o /usr/local/bin/weave sudo chmod a+x /usr/local/bin/weave
  3. Setup Weave:
    weave launch weave expose
  4. Route traffic into the VM
    sudo route add -net 10.32.0.0/12 <VM_IP> sudo route add -host 172.17.0.1 <VM_IP>
  5. Run a container on Weave, and get it’s IP
    docker run --interactive --net=weave alpine sh hostname -i # 10.32.0.2 172.18.0.2
  6. While the container is running, run from the host:
    ping 10.32.0.2

(Blackxored) #2

I can also confirm this.