port is already allocated without running containers

[oliverhr]

Expected behavior

Container creation

Actual behavior

Error: port is already allocated

Information

Diagnostic ID: 269F8ACE-C09C-4FB4-856C-8208C92B0020
Docker for Mac: 1.12.0-beta21 (Build 11019)
macOS: Version 10.11.6 (Build 15G31)
[OK] docker-cli
[OK] app
[OK] moby-syslog
[OK] disk
[OK] virtualization
[OK] system
[OK] menubar
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

1. Run a container using -p with any port - in my case two containers nginx (80, 443) and a node app running on 10011
2. Remove the container
3. Create the same or another container on the same port

---

Result for command docker ps -a:

Portscan on 0.0.0.0 with docker running - But without running any container

Portscan on 0.0.0.0 without docker:

[oliverhr]

Problem remains even after uninstall beta version and install stable.

[oliverhr]

Solution:

I don't like but – It is what it is

[jamesdixon]

Also seeing this when my mac sleeps and this is woken up; containers are killed (issue #85) and then when trying to restart containers using docker-compose up, I'm seeing the above error. Only fix is to restart my machine :(

[qxhy123]

same here, reset to factory defaults would fix that.

[jamesdixon]

In addition to this and #85, it's making development very difficult. Any additional information/assistance I can provide to help?

[sergeyklay]

The same issue on OSX 10.11.6 with Docker 1.12.1 stable

[djs55]

@sergeyklay could you upload diagnostics from a reproduction on 1.12.1? The diagnostics in 1.12.1 are much better than in 1.12.0, in particular they include a process list from inside the VM which would show ports being held open from there. (The port opening is requested by the docker engine by running a proxy process, which communicates with a server on the Mac which actually opens the port. When the process inside the VM quits, the ports are closed on the Mac)

It would also really help if someone could help me reproduce this. Has anyone got a simple script or compose file they could share? Every time I try to repro this it always seems to work as expected :(

For example if I run an nginx in one terminal:

$ docker run -it -p 80:80 -p 443:443 nginx

and then in another terminal

$ curl http://localhost
... lots of html ...

I can see the ports bound via netstat:

$ netstat -an | less
Active Internet connections (including servers)
Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)    
tcp4       0      0  *.80                   *.*                    LISTEN     
tcp4       0      0  *.443                  *.*                    LISTEN  
...

I can then Control+C the docker run and the ports go away. If I run docker run again it all comes back as expected :(

For a more complicated example, if I clone the example-voting-app:

$ git clone git://github.com/docker/example-voting-app
Cloning into 'example-voting-app'...
remote: Counting objects: 238, done.
remote: Total 238 (delta 0), reused 0 (delta 0), pack-reused 238
Receiving objects: 100% (238/238), 182.09 KiB | 0 bytes/s, done.
Resolving deltas: 100% (71/71), done.

I can repeatedly bring it up and down with

$ docker-compose up -d
# manually verify that ports 5000 and 5001 are bound
$ docker-compose down
# manually verify that ports 5000 and 5001 are free

with no error :(