Docker Community Forums

Share and learn in the Docker community.

Docker doesn't play nice with OSX Application Firewall


(Ogapo) #1

Expected behavior

When mapping a container to a host port, I should be prompted to allow the application to open the port in the firewall.

Actual behavior

No prompt occurs and I cannot contact opened ports without disabling the Application Firewall entirely.

Information

OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.1-beta13.1
Running diagnostic tests:
[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/20160529-235912.tar.gz
Most specific failure is: No error was detected
Your unique id is: 41E907C0-88CD-4B92-A179-2CCB0F8FB406

Steps to reproduce the behavior

  1. Run any container and map an internal port to a host port.

(Musitproject) #2

Just to verify, I experience the same. No registry of service when I start docker engine and I can’t access docker containers outside the machine.

I can’t even use my usual proxy trick as a work around as the ports are bound already


(Diarmuid) #3

I’m having a similar issue. Can’t connect to privileged ports from outside my host with the application firewall enabled.

https://forums.docker.com/t/lan-access-to-privileged-ports-1024/15314