Rancher Desktop
An open-source desktop container environment for Windows, macOS and Linux that lets developers choose between containerd and Moby dockerd and optionally run local K3s Kubernetes.
What Rancher Desktop provides
Rancher Desktop creates a local container and Kubernetes development environment. It can expose Docker CLI and Docker API through Moby dockerd, or use containerd with nerdctl, and it can run a local K3s cluster when Kubernetes is required. It is a desktop runtime rather than Rancher Manager for centralized cluster administration.
Runtime and reset boundaries
containerd and Moby are alternatives, so only one runtime is active at a time. After switching, images and workloads from the previous runtime are not visible in the new view. Kubernetes upgrades usually retain resources, while a downgrade or Reset Kubernetes may remove workloads; Factory Reset also removes application settings. Export state before changes.
Maintenance note
This page reviews Rancher Desktop 1.24.0, runtime selection, K3s lifecycle, CLI contexts, ports, volumes and reset or backup boundaries. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Rancher Desktop to this cloud drive
Baidu Netdisk
Save Rancher Desktop to this cloud drive
Rancher Desktop 1.24.0 runtime and K3s setup guide
Install the matching build, choose containerd or Moby in a test environment, verify the corresponding CLI context, and enable K3s only after saving the state that a reset could remove.
Before you start
- Prepare a Windows, macOS or Linux host with hardware virtualization and enough disk and memory for containers, volumes and K3s.
- Record existing Docker contexts, Kubeconfig files, ports and other desktop runtimes to avoid socket or port conflicts.
- Back up images, named volumes, databases, Kubernetes manifests and secrets, separating rebuildable configuration from unique data.
Installation steps
- 01
Install the 1.24.0 package
Use the Windows x64 MSI, the matching macOS Intel or Apple silicon build, or the Linux package, then check virtualization and application status.
- 02
Select a container runtime
Choose Moby dockerd for Docker CLI, Docker API and Compose workflows, or containerd for nerdctl and Kubernetes-oriented work; decide in a test environment before importing data.
- 03
Configure K3s and resources
Leave Kubernetes off when it is not needed. When enabled, select a supported version, set CPU, memory, disk and ports, and check whether Traefik uses 80 or 443.
Quick start
- 01
Verify CLI and namespace
Run a disposable container with Docker CLI in Moby mode or nerdctl in containerd mode, and confirm it is connected to Rancher Desktop rather than another runtime.
- 02
Test ports and persistent storage
Start a test service with a port mapping and dedicated host directory, create a named volume, then check access, permissions and data after restart.
- 03
Test K3s lifecycle
Deploy a small stateless workload, inspect context, Service and logs, then disable and re-enable Kubernetes to confirm the expected state before expanding usage.
Usage tips
- containerd and Moby are mutually exclusive; switching makes the old runtime's images and containers invisible but does not make unbacked data safe to delete.
- Kubernetes can be disabled to save resources. Export manifests and stateful data before version changes, Reset Kubernetes or Factory Reset.
- Container sockets, host-directory mounts and Kubernetes credentials are high-privilege interfaces; keep them off untrusted networks and containers.
Troubleshooting and uninstall
Why do Docker or nerdctl show different containers from the UI?
Confirm the active runtime, CLI context, namespace and environment variables. A runtime switch changes the visible image and container store.
Why does K3s fail to start or kubectl use the wrong cluster?
Check resource limits, Kubernetes ports, Traefik bindings, the current Kubeconfig context and other local clusters before collecting diagnostics or considering a reset.
- Export container and cluster stateStop writes, export images, named volumes and databases, save manifests and secret backups, and verify a restore before removal.
- Uninstall and decide on virtual dataExit Rancher Desktop and uninstall through the platform. Remove virtual disks, caches and contexts only after confirming that all unique data is backed up.
Frequently asked questions
Should I choose containerd or Moby dockerd?
Choose Moby for Docker CLI, Docker API and common Compose workflows; choose containerd for nerdctl and a Kubernetes-oriented runtime. Only one is active at a time.
Does disabling Kubernetes delete workloads?
Normal shutdown preserves resources for the next start. Downgrades, Reset Kubernetes and Factory Reset have stronger cleanup effects, so export manifests and stateful data first.
Is Rancher Desktop the same as Rancher Manager?
No. Rancher Desktop is a local developer environment, while Rancher Manager centrally administers Kubernetes clusters.