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

Docker Desktop
1

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

2

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.

3

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

1 Like
4

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.

5

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

6

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…

7

Yes. Same here. Updating to latest Docksal version failing due to driver failed programming external connectivity on endpoint docksal-vhost-proxy.

Screenshot 2020-02-20 at 12.20.55 AM
Screenshot 2020-02-20 at 12.20.55 AM2282×302 44 KB

8

latest updates related to this error we can track (for Mac) at https://github.com/docker/for-mac/issues/4209

Temporary solution:
Downgrading to v2.1.0 solves the issue for me.
https://download.docker.com/mac/stable/40693/Docker.dmg

9

Issue still exists on 2.2.0.4, engine 19.03.8 :frowning_face:

10

Tried 2.1.0.5 again on my local. The new GUI features promised were too tempting not to try again. Bummed like everyone else above. Returning to 2.1.0.5

fin project start
 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 (9443bb5547db8ef71b9fa8a29fb74483f0ce754a4e1941f21418c72e1dc7de22): Error starting userland proxy: listen tcp 192.168.64.100:443: bind: cannot assign requested address.
 ERROR:  Failed starting the proxy service.
11

As mentioned by @bttvs above, best is to continue this discussion on the bug tracker located here: https://github.com/docker/for-mac/issues/4209

The more votes we get there the higher the chance that the developers look into this.

I do not think they monitor this user forum.

12

Posted ^^^ on GitHub.

1 Like