docksal: Failed to start the proxy servies.

I was able run docksal on this machine Yesterday. Today when i try to fin up – it gave me an error, an i tried to reconfigure.

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

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 16 (6 by maintainers)

Most upvoted comments

For anyone coming upon this thread in the future: it may be a version compatibility issue. If you’re running mac docker desktop 2.2.0, you need to downgrade docker desktop to 2.1.0. As of this writing, this issue exists with docksal 1.13.1 and (I think) every previous version. Presumably, at some point, this will be fixed in docksal.

MKorostoff on Mar 3, 2020

This issue is documented in the troubleshooting section of the docs: https://docs.docksal.io/troubleshooting/common-issues/#issue-05

lmakarov on Feb 6, 2019

@greg-marra something is not very right with your environment at all.

/usr/local/bin/fin: line 117: cmd.exe: command not found
...
/usr/local/bin/fin: line 5736: wmic.exe: command not found

cmd.exe and wmic.exe are basic windows utilities that should be present on the system. I suppose something is wrong with $PATH (%PATH%) variable on your system.

Try running wmic.exe in the Ubuntu shell directly (you use Ubuntu right?). If it does not work then it is something with your setup. I could try guessing what if you show echo "$PATH" output from the Ubuntu bash shell and also show output from regular Command prompt of the set command.

achekulaev on Apr 18, 2019

It is not known why this happens, it is not related to Docksal. It is something in VBox or Docker. Try restarting your host machine.

achekulaev on Feb 6, 2019