Toggle Container Runtime - Descriptions and Wording

[rak-phillip]

#900 will introduce the ability to select a container runtime on first launch of Rancher Desktop. This decision can be perceived as a big one, especially to new users who might be trying out Rancher Desktop for the first time; other's might not might not be aware of the difference between dockerd and containerd and wont necessarily know the benefits of choosing one over the other.

Because this has potential to be such a confusing option on first launch, I want to make sure that we have effective messaging that will help people understand the decision they are making. There are at least two problems that we need to address:

1. Make sure that labels for our options are accurate and clear (Currently Container Runtime, with two options, dockerd (moby) & containerd
2. Provide content for a tooltip that will explain the difference between the two and why one would want to pick one option over the other. (I'm also considering that we might want to emphasize that this can be changed later)

Making a selection

Tooltip active

[mook-as]

It may be better to provide option-specific help rather than help for the whole section:

• dockerd (moby)
  • Provides better compatibility with Docker tooling.
• containerd
  • Provides better compatibility with Kubernetes-native applications.

[jandubois]

The description should tell the user the actual benefit they get, and not just describe the feature. It has to answer the questions: "Why do I want it? What can I do with it?"

• dockerd (moby)

  • Provides better compatibility with Docker tooling.

• Provide native docker API; use with docker cli and k3d.

• containerd

  • Provides better compatibility with Kubernetes-native applications.

What actually is the "better compatibility"? We could say "less resources", but we need to measure first to know if this is noticeable.

• Separate namespaces for regular and kubernetes container images; use with nerdctl.

Not really happy with these either, but they show the direction I want to change to.

[rak-phillip]

Updated the mockups to reflect the feedback. Reduced the descriptions so that they easily fit on a single line. How do you feel about this change compared to what we originally had above?

Making a selection

@mook-as @jandubois

[mook-as]

CLI is an initialism ("command line interface") and should be all upper case. The tools themselves are typically lower case (and so they're fine as-is).

For containerd, I was initially thinking that other Kubernetes-focused tooling are more likely to deal with containerd (e.g. kim); however, maybe that's a special case and people normally don't use things that go that low-level…

[jandubois]

I don't know what "native" means here; I think it is redundant. Either you support the docker API, or you don't.

[rak-phillip]

Thanks! Updated to reflect the feedback