Docker Desktop Resource Saver Quietly Kills docker-mac-net-connect

[pfandzelter]

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.

[gregnr]

@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.

[lcmen]

I'm experiencing the same issue with the latest Docker Desktop. When Docker Desktop goes into resource saver mode, then docker-mac-net-connect does not re-provision VM after it's woken up. I need to restart docker-mac-net-connect via sudo brew services restart docker-mac-net-connect to be able to connect to containers via their IP again.

How can I further debug it to provide more information for the investigation?

[lcmen]

@pfandzelter where you able to solve this issue without disabling Resource Saver option?

[gregnr]

@lcmen you can try the instructions under general troubleshooting to run docker-mac-net-connect manually and see if there is anything noteworthy in the logs