New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to use "fin system reset" with new Docker Desktop 2.3.0.2 for Mac #1342
Comments
Looks like yet another regression from upstream... docker/for-mac#4541 |
I can confirm here that things are working again after updating to current docker Desktop for Mac Version 2.3.0.2.
|
@42robotsCS to test this specific issue you need to perform your steps above, but then restart the Docker Desktop. Follow the steps given in the OP. The @lmakarov yes, I meant to post that link also. I agree that is looks very much like still a problem upstream. At least in this case there is a workaround for it in Docksal. |
I've looked at what's going on with the new Docker Desktop. Below are my findings. After the upgrade from upgrade from Docker Desktop 2.1.x.x to 2.3.0.2, docksal-vhost-proxy and docksal-dns system service are down:
Checking why:
That ^ is exact what #1268 was about. Resetting and rechecking system services:
Note how the PORTS section now reads Trying to talk to vhost-proxy:
Starting any Docksal project, then checking vhost-proxy again:
Resetting docksal-vhost-proxy with a project running:
Success! Finally able to connect to vhost-proxy from the host. Stopping the project (all active projects), then resetting the vhost-proxy and checking:
We are back to square one with vhost-proxy not working. It looks like vhost-proxy is only accessible from the host when it is connected to at least one project network. Creating a bridge network manually and connecting vhost-proxy to it does not help:
|
Here's a workaround for the time being for this issue (and actually, for #1268 on Docker desktop 2.2.x.x versions):
This removes the IP binding, so vhost-proxy will be exposed on all local interfaces. With this in place, no additional steps are required after restarting Docker Desktop. |
Hmm, this didn't work for me. I did the two commands mentioned above. Then I restarted Docker Desktop and did a I'll try to get time to do more debugging using some of the other commands you used above to try and determine why this didn't work for me. |
@mike-potter There is one more issue that gets in the way here - the |
Should be fixed in v1.13.3 (just released). |
Description
After upgrading to Docker Desktop 2.3.0.2 for Mac OSX, local
*.docksal
sites are not accessible after restarting Docker Desktop. After doing afin start
for the project, afin system reset
command is required to get the sites working.Steps to reproduce the issue:
fin start
to start the docker containers.fin system reset
Output of
fin config
:fin config output
Output of
fin sysinfo
:fin sysinfo output
The text was updated successfully, but these errors were encountered: