Docker Community Forums

Share and learn in the Docker community.

Docker not opening lower ports in firewall


(Fridder) #1

Expected behavior

Ports like port 80 should be accessible outside the host

Actual behavior

Ports are inaccessible unless the Mac Firewall is turned off


(Fridder) #2

Also this doesn’t seem to be happening on all of my co-workers macs. I am not seeing anything obvious in the logs and am wondering what I should check to try and fix


(Fridder) #3

24D251E8-966D-4A15-92D2-CBDF56E23B8B

Docker for Mac: version: mac-v1.12.0-beta18-3-gec40b14
OS X: version 10.11.5 (build: 15F34)
logs: /tmp/20160711-093106.tar.gz
[OK] docker-cli
[OK] app
[OK] menubar
[OK] virtualization
[OK] system
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

Looks like my coworker had their firewall off. I wonder if this has to do with the change where non-admin users could install and use docker for mac considering this seems to only affect privileged ports.


(Fridder) #4

Still an issue with the latest beta. I created an issue on the VPNKit repo as well.


(Samifruit514) #5

Same problem here. Maybe this is something to do with pfctl or /usr/libexec/ApplicationFirewall/socketfilterfw --unblock ??

Note that running an apache server on the mac osx host on port 80 works perfectly. so I confirm that its related to docker


(Adam Englander) #6

Has this been acknowledged by the Docker team? All I can find in the forum are duplicate issues and plenty of horrible hacks out there to compensate. I really need to know if this is being worked on?


(David Sheets) #7

This issue is tracked by https://github.com/docker/vpnkit/issues/92.