Try to run two docker instances attempting to map the same port on these two new IP addresses (in separate terminals):.$ sudo ifconfig lo0 add 127.10.0.1 netmask 0xffffffff Host distribution: OS X El Capitan Version 10.11.4 Steps to reproduce the behavior Reproducible case: see “steps to reproduce” or 'actual behavior' Most specific failure is: No error was detected $ docker run -it -rm -p 127.10.0.1:4444:4444 appropriate/nc -l 4444ĭocker: Error response from daemon: driver failed programming external connectivity on endpoint serene_torvalds (7cc7c5e6ad2ac75f7285a067dae239f567d608c0f96283ac2adc9d32ace2f00d): Error starting userland proxy: failed bind vsock connection to ffffffff.0001115c, returned -1.ĭocker logs are being collected into /tmp/

$ docker run -it -rm -p 127.10.0.2:4444:4444 appropriate/nc -l 4444ĭocker does not allow me to map the same port on a second IP address: $ sudo ifconfig lo0 add 127.10.0.1 netmask 0xffffffff I’ll be able to connect to these listening ports separately using (for example) telnetįrom Docker I would expect this similar functionality to work properly: $ docker run -it -rm -p 127.10.0.1:4444:4444 appropriate/nc -l 4444 $ sudo ifconfig lo0 add 127.10.0.2 netmask 0xffffffff When not using docker it’s possible on Mac OS X: $ sudo ifconfig lo0 add 127.10.0.1 netmask 0xffffffff I should be able to map one port on different IP addresses from different containers.

Docker for mac beta ip