Be more explicit about what running without administrative rights means

I’ve seen several reports from Rancher Desktop 1.3.0 that show the docker socket is not available. In most (all?) of them the reason was that the user requested to run without administrative rights, and didn’t realize that this means that they have to switch docker contexts to use the docker cli.

In addition to providing a more prominent explanation, we could also go further in offering the user to switch the context to rancher-desktop for them.

[jandubois]

I think that we can reword the Sudo Dialog to something like this

I think that will help a bit, but I think we should also follow up with a dialog offering to change the context under the following conditions:

• admin access refused
• container runtime is moby
• current docker context is not rancher-desktop

We would need to trigger the dialog also when the user switches from containerd to moby, or disables admin access in the app settings (again, if all the conditions above are true).

I assume we don’t need to bother with the --no-modal-dialogs option here because we should not be able to get to a point where this additional dialog would be triggered because the initial dialog would already be suppressed.

[cdivita]

I would say that the Docker context change should be automatic under the conditions highlighted by @jandubois, otherwise it will not possible to work with the Docker (moby) daemon started by Rancher Desktop.

The automatic Docker context change could be part of the Application settings and it should be selected by default (explaining the steps required to change it manually)