I was working on a VPN connection and noted that I had to set networking to hostnet to get npm connectivity for my image builds. My published ports appeared on the host as expected. Then the latest beta upgrade landed and I applied it.
docker-compose up'd my project again, but connections to my container started failing. Looking at
docker ps and
lsof output I noticed that the published ports are listening on the VM IP, not the host.
pinata list still shows networking to be set to
Still in hostnet mode, published ports still visible on host after upgrade.
Reverted to nat networking(?).
The particular VPN client is Tunnelblick.
the output of:
pinata diagnose -uon OSX
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta8.2
Running diagnostic tests:
[OK] Moby booted
Docker logs are being collected into /tmp/20160421-185637.tar.gz
Most specific failure is: No error was detected
Your unique id is: F68A8050-2593-4AD1-8E01-E9BFE38F55C3
Please quote this in all correspondence.
Steps to reproduce the behavior
- Turn VPN off
pinata set network hostnet
docker-compose upsomething that publishes ports
- observe ports on localhost
- Upgrade Docker for Mac
- observe ports not on localhost