https://rancher.com/ logo
Join Slack
Powered by
Why does Rancher desktop take so very long to star...
# rancher-desktop
e
Why does Rancher desktop take so very long to start up, compared to other Docker providers? (Windows, but macOS too I think). It is plenty fast after startup, but wow, I'm already 4 minutes in this time (Windows). Spends a lot of time "Initializing WSL data" (kubernetes is not enabled)
f
It should not take more than 1-2 minutes; I suspect something is wrong
e
Always the case for me. But even 1-2 minutes is vastly longer than any other docker provider.
f
First time after install/factory-reset or every time?
To start an existing instance (including Kubernetes) takes 35s for me on macOS
e
Certain every time I upgrade. But I just did another start after upgrade and it was under a minute.
But on upgrade it took forever. I just look away. (Sometimes I only start it to test new versions)
f
Idk. It is slower on Windows, but it depends a lot on the machine you run on
e
I guess not to worry, but it really is striking every single time I use RD
This is a very hefty machine with lots of memory
I'll pay attention next time I run on macOS
f
Thanks for letting us know!
👍 1
I just installed 1.20 on a Windows machine with an older version, and it took 45s to get ready (no Kubernetes, using 
containerd
). 🤷
👍 1
e
Certainly not my experience, but still RD is many times slower always than all other Docker providers. 45s is very slow by comparison to all the others.
f
Like which others? Lime/Colima take the same time to start the VM
e
Lima, Colima, Orbstack, Docker Desktop
f
Copy code
limactl start -y <template://docker>  2.72s user 2.55s system 12% cpu 43.671 total
So Lima also takes 45s for a fresh start. Surprisingly colima started in 17s, need to take a look because it is also based on Lima
👍 1
e
RD is absolutely an outlier
My latest startups on macOS didn't take long
f
We have looked at this a bit, and I think Mark found a way to cut startup time on Windows in half. The gains on macOS are more modest. The biggest issue is that there is a probe in Lima that checks every 10s if ssh is ready. And for some reason we often take just over 10s, so the wait becomes 20s. 😞
So we will have some improvements, but there are other things that will have to wait until we move away from running on Alpine ISO images
e
I just noticed that I was using sshfs (is that still default?) and changed to virtiofs (which ought to be default these days?)
f
The default in 1.20.0 should be VZ and virtiofs for a new install, or after a factory reset. We will not change an existing config.
Please let me know if this is not working correctly for you
e
It's just followed me then I guess. I'll check our DDEV test runners and make sure they got changed.
f
Thanks for keeping me updated!
👍 1
28 Views
Open in Slack
PreviousNext
Powered by