This message was deleted.

No; we just set up a separate docker context (and if sudo is disabled, switch to it). Actually, we should be shipping a pretty unpatched version of the

docker

CLI.

confirmed. i was getting random behaviour with both. it threw me off. I am assuming it was caused by things restarting in the VM?

Likely, but the progress bar wasn't supposed to go away until the VM is ready. Out of curiosity, are you running Kubernetes? (That is, is the Enable Kubernetes checkbox in Rancher Desktop checked?)

yep. but not 'using' it yet. i wait for it to start but i am mostly issuing docker build/create/run commands only

Right, I was wondering if it's something like you're not enabling it and then we finish waiting too early. But that doesn't sound like it.

could not reproduce this today with a simple startup. as soon as virtual machine was up according to the UI (and k8s, services were still loading),

docker images

worked every time