docksal: Updating to Docker Desktop 2.2.0.0 breaks Docksal

Here are the direct links to the latest 2.1.x version (2.1.0.5): Mac: https://download.docker.com/mac/stable/40693/Docker.dmg Windows: https://download.docker.com/win/stable/40693/Docker Desktop Installer.exe

I can confirm this bug when upgrading to Docker Desktop 2.2.0.0 on macOS resulting in:

Error starting userland proxy: listen tcp 192.168.64.100:443: bind: cannot assign requested address.

Going back to Docker Desktop Version 2.1.0.5 resolves the issue for now.

Also confirming that if you restart Docker Desktop and then do a fin start, the project site no longer responds. Still have to do a fin system reset to get the site to work again. Once that is done, doing fin stop and fin start seem to work fine.

So you just need to use fin system reset after rebooting or restarting Docker Desktop. Hopefully this is something that can be fixed on the Docksal side. The bug that prevented Docker Desktop 2.2 from working DOES seem to be resolved. Needing to use fin system reset is a new issue.

Confirmed that this issue is resolved after upgrading to edge 2.2.3.0.

It also seems strange to upvote a “solution” that is a downgrade. It’s ok that we can all downgrade to get around the issue, but it should not be considered a good solution to downgrade. If anything a downgrade “solution” should get a thumbs down. ??

@danshumaker Downgrading is a temporary workaround. The actual issue is upstream in Docker for Mac/Win. Chiming in there will make the most sense.

Upstream issues:

• https://github.com/docker/for-mac/issues/4209
• https://github.com/docker/for-win/issues/5546

Opened new issue #1342 to track this.

The latest stable Docker Desktop versions (released today) should address this regression:

• Docker for Mac 2.3.0.2 (download) - CONFIRMED

Fixed an issue where a container port could not be exposed on a specific host IP. See docker/for-mac#4209.

• Docker for Windows 2.3.0.2 (download)

Fixed an issue where a container port could not be exposed on a specific host IP. See docker/for-win#5546.

On my mac with catalina (10.15.4) it works with edge 2.2.3.0 , but I have to run always “fin system reset” after “fin project start”, because the dns to “whatever.docksal” is not working.

Still not working for me.

Docker:

Docksal: $ fin version fin version: 1.93.0 $ fin start ALERT: Some Docksal services were not running Restarting Docksal system services… Configuring network settings… Resetting Docksal system services…

• proxy docker: Error response from daemon: Ports are not available: listen tcp 192.168.64.100:443: bind: The requested address is not valid in its context. ERROR: Failed starting the proxy service.

Would be nice to mention a specific supported version on https://docs.docksal.io/getting-started/setup/#install-macos as it took me a while to get to this discussion.

While it may be an upstream issue, I don’t think it impacts only docker/for-mac. The same issue impacted all of our Windows users when they upgraded to 2.2.0

You are correct, it is also an issue for windows. See: https://github.com/docker/for-win/issues/5546

One gets the same error with the Windows 10 version of Docker 2.2.0.0

Right now the solution is to downgrade Docker to 2.1.x