Docker Community Forums

Share and learn in the Docker community.

DockerDesktop on Mac 2.2.0.0, not able to Bind with Port 443

Installed Docker Desktop 2.2.0.0 and now I can not start a docksal project. According to Google another app is running on the 443 port but this is not true.

The error is - docker:Error response from daemon: driver failed programming external connectivity on endpoint docksal-vhost-proxy (7004fff7a84bd9e4fab301ce1c65429c9aade139efdc65dec95f83b5a2e46555): listen tcp 192.168.64.100:443: bind: cannot assign requested address.

Here’s the output from fin status:

ALERT: Some Docksal services were not running
Restarting Docksal system services…
Configuring network settings…
Configuring NFS shares…
NFS shares are already configured
Resetting Docksal system services…

  • proxy
    docker: Error response from daemon: driver failed programming external connectivity on endpoint docksal-vhost-proxy (fcf1c9f83ad3acc85042b2e84bed773ee24da6930ff192d8b7d2535b66a1f620): listen tcp 192.168.64.100:443: bind: cannot assign requested address.
    ERROR: Failed starting the proxy service.

2017 Macbook Pro
Mojave 10.14.6

Yeah, same here. The problem appears to be that docker is not able to bind to ports on IP addresses other than “unspecified” or 127.0.0.1

% docker run -p 127.0.0.1:4443:443 -it --rm hello-world

Hello from Docker!
(..)
% docker run -p 4443:443 -it --rm hello-world

Hello from Docker!
(..)
% docker run -p 192.168.28.82:4443:443 -it --rm hello-world
docker: Error response from daemon: driver failed programming external connectivity on endpoint mystifying_ritchie (186ef8bc7cffec5ae617929a562bb42a5f6add3990ccfa510e642e20e50278b8): Error starting userland proxy: listen tcp 192.168.28.82:4443: bind: cannot assign requested address.

% lsof -i :4443
%

192.168.28.82 is my workstation’s IP address and nothing is listening on 4443. Before the upgrade to 2.2.2.0 everything worked alright.

Solved Docker Desktop issue by uninstalling 2.2.0.0 and installing 2.1.0.5. Luckily I only have one site running on Docker

3 Likes

I can confirm I am experiencing the same issue with 2.2.0.0 on Mojave 10.14.6: unable to bind to a port when specifying an IP address.

I need this because I want a container only to be listening on a specific VLAN on my machine.

With 2.1.0.5 all is working as expected, so I too reverted to that version.

Best regards,
Hollie.

I can confirm that rolling back to 2.1.0.5 fixes this problem. Pretty bad issue.

Just tried with version 2.2.0.3 and

  • Engine 19.03.5
  • Compose 1.25.4

And I still get this error. Was hoping the latest update fixed it…