You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running into issues with the docker-mac-net-connect service since Docker Desktop v4.24, which enabled Resource Saver by default. Resource Saver kills the Docker VM if no containers are run for 5 minutes in order to save resources (see here). Obviously that's a great feature that I want to keep enabled, but it quietly breaks docker-mac-net-connect whenever it kicks in as the VM-side component don't restart as soon as the VM is started anew. I'm looking to fix this in a PR, but for now I want to report this just in case other people run into this. The workaround for now is to either disable Resource Saver or restart docker-mac-net-connect whenever you want to use it.
The text was updated successfully, but these errors were encountered:
@pfandzelter Thanks for the heads up. docker-mac-net-connect does have logic that auto-resets itself when it loses connection and reconnects to the Docker daemon, so I'm a bit surprised it's not working in this context. Looking forward to seeing what you find out.
I am running into issues with the
docker-mac-net-connect
service since Docker Desktop v4.24, which enabled Resource Saver by default. Resource Saver kills the Docker VM if no containers are run for 5 minutes in order to save resources (see here). Obviously that's a great feature that I want to keep enabled, but it quietly breaksdocker-mac-net-connect
whenever it kicks in as the VM-side component don't restart as soon as the VM is started anew. I'm looking to fix this in a PR, but for now I want to report this just in case other people run into this. The workaround for now is to either disable Resource Saver or restartdocker-mac-net-connect
whenever you want to use it.The text was updated successfully, but these errors were encountered: