Changing WiFi network makes the services stuck

[waszabi]

Describe the bug

This happens when transferring the MacBook to another office where there is a different WiFi. For instance there are 26 containers running in total. The lid is closed and then it is opened on a different WiFi. Number of running containers is lower (e.g. 12) and they do not work properly. The workaround is to open Activity Monitor and search for "Virtual Machine Service" then double click on it and choose the Quit option. Afterwards, OrbStack says "Service Not Running" and there is a button to start it. Then it loads all the containers and it works properly. Is it please possible to fix this?

To Reproduce

No response

Expected behavior

No response

Diagnostic report (REQUIRED)

OrbStack info:
Version: 1.5.1
Commit: 4cfac15e1080617c70eb163966e1cb2009dac1c2 (v1.5.1)

System info:
macOS: 12.7.4 (21H1123)
CPU: amd64, 4 cores
CPU model: Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz
Model: MacBookPro13,1
Memory: 16 GiB

Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-04-29T09-08-34.135049Z.zip

Screenshots and additional context (optional)

No response

[slinorb]

Please elaborate on "they do not work properly.". What are the symptoms? The containers are not running? Or can not access containers.

[waszabi]

It is very random. Normally there are 26 containers running. After opening the lid on other WiFi network there is sometimes 12 containers running, sometimes only 2, it varies each time. For instance the web servers cannot be accessed from the browser. The command docker ps also does not work, it only shows an empty line in the terminal and does not output anything just hangs. So "they do not work properly" could be rephrased as some containers stop for unknown reason and cannot be accessed.

This does not happen when the WiFi network is not changed.

[waszabi]

Docker is in Swarm mode

[deniscsz]

I'm facing the exactly same issue. All the commands in the container terminal got "stuck" like a infinite loop. I'm waiting for 20min for a simple ls. Any command in the terminal behaviors as the same. For me it happens using cable or wifi, or even "offline".

The log of the containers works normally. Others containers are running normal (of other projects that I started after the problem come up).

I tried uninstall and reinstall the last version and the problem still happens. I already rebuilt the container/images without success too.

Version 1.5.1 (16857)

[kdrag0n]

@waszabi @deniscsz Can you try v1.6.0 Canary? Settings > Update channel

[deniscsz]

@kdrag0n Sure, I'll try it right now.

[deniscsz]

@kdrag0n After change to v1.6.0 Canary and rebuild the image, it works. Thank you.

[kdrag0n]

Great! Thanks for testing.

[kdrag0n]

Released in v1.6.0.

New: Truly fast container filesystems on macOS: 2–10x faster, within 75-95% of native

[waszabi]

Thank you for fixing this! It looks that it works.