rancher-desktop Rancher desktop is extremely volatile

Actual Behavior

Hi, recently our company decided to use Rancher Desktop instead of Docker Desktop. The transition went pretty smoothly but every day we are facing struggles when using the application. Containers stopped responding all of a sudden, the "Containers" page is stuck looping at "Loading", and I need to restart Rancher Desktop to make it work, making me lose swathes of time.

Sometimes, I can't even restart it, it gets stuck on "unloading" and I have to restart the computer.

Steps to Reproduce

Just go over your day, and experience crashes

Result

Rancher Desktop stops responding

Expected Behavior

Rancher Desktop doesn't stop responding

Additional Information

Sometimes I get this error: CleanShot 2023-12-12 at 10 23 48@2x

Rancher Desktop Version

1.11.1

Rancher Desktop K8s Version

not using

Which container engine are you using?

moby (docker cli)

What operating system are you using?

macOS

Operating System / Build Version

macOS 14.1.1 (23B81)

What CPU architecture are you using?

arm64 (Apple Silicon)

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

No response

Dec 12 '23 08:12 mallowigi

@mallowigi , Thanks for filing the issue. Good to know the initial transition was smooth.

On the Container Dashboard problems, it's a feature that we recently added which is still experimental and is evolving in terms of stability and functionality. It would be great if you can share the repro steps and the application logs when you run into problems to help us investigate issues. You can open the folder containing the Rancher Desktop application logs via Troubleshooting > Show Logs button.

Also, when Rancher Desktop gets stuck any point, you can run the rdctl factory-reset command to terminate the app. However, please note that the factory reset command takes the app to a clean slate state and removes all your workloads and any configuration you may have done etc. For some users, factory reset offers a better solution than machine restart even though I understand both are painful.

Dec 12 '23 16:12 gunamata

It's a bit hard to reproduce as I am unable to share the code by company policy... But from what I can share, if that's relevant to you:

There are three containers that run a Node.JS with Nest.js. They each have a /health endpoint that I use with command in docker-compose file by the help of curl
Another container, the "gateway", is supposed to run once the three other containers are up and running. For that I am using the service_healthy directive to ensure it runs after they are healthy.

This will work for some time but as soon as time passes, the service starts becoming unresponsive. At this point if I try to do docker-compose down or try to restart Rancher, the application loops forever, until I restart the computer again.

I can see a lot of logs in that folder, which one is interesting?

FYI, we're using a lot of experimental features from RD since they are our only replacement for the original Docker: moby, virtiofs, Rosetta support, ZFS...

Dec 12 '23 16:12 mallowigi

Thanks for the additional information. For the logs, if it's possible please zip the entire logs folder and share it. If it's not possible to share the full folder then the files background.log, docker.log, diagnostics.log, networking.log , moby.log, lima.log would be helpful for the preliminary investigation.

Dec 12 '23 17:12 gunamata

Archive.zip

Dec 13 '23 07:12 mallowigi

It could be a red herring but I see below message in the lima.log.
@Nino-K , Any thoughts on what could cause this and any suggestions to try out please?

time="2023-12-12T18:33:17+02:00" level=debug msg="Failed to look up socket_vmnet path \"/opt/socket_vmnet/bin/socket_vmnet\"" error="exec: \"/opt/socket_vmnet/bin/socket_vmnet\": stat /opt/socket_vmnet/bin/socket_vmnet: no such file or directory"

Dec 13 '23 20:12 gunamata

Please note that it also happens sometimes when I go back to my computer after sleep.

Dec 14 '23 06:12 mallowigi

Thanks for opening this issue, I have the same exact problem as you but on a Windows 10 PC. Wish I could find the cause but for now, I need to restart my PC from time to time. This issue has been happening to me for a few months now (ever since installing Rancher Desktop when my company moved away from Docker Desktop licensing changes).