**File not scanned for virus due to size.**$$$$$$Release Notes for 1.23.1$$$Kubernetes portforwarding on macOS and Linux has been fixed$$$In the 1.23.0 release Kubernetes port were not being forwarded to the host. This has been fixed.

**File not scanned for virus due to size.**$$$$$$Release Notes for 1.23.0$$$Whats New$$$Dark mode preference$$$Rancher Desktop now lets you choose between dark; light; and system themes under Preferences > Behavior. Previous versions always followed the OS theme. (#5905)$$$$$$Container dashboard improvements$$$Thanks to @endemics; the container detail page now includes a Shell tab that opens an interactive terminal session inside a running container. The session persists across tab switches; so you can check logs and return to your shell without losing context. (#9925)$$$$$$@endemics also added an Inspect tab that displays key container metadata pulled from docker inspect: name; image; IP address; creation date; and collapsible sections for mounts; environment variables; commands and arguments; capabilities; ports; and labels. (#9986)$$$$$$A Stats tab; also from @endemics; shows live CPU; memory; network; and disk I/O charts for a running container; plus a table of its processes. The refresh interval defaults to one second; with 5-second; 20-second; 30-second; and 1-minute options; collection stops when you leave the tab. (#9987)$$$$$$Separately; @officialasishkumar added a Restart action to the Containers list for running containers; available for single containers or bulk selections. The table refreshes once the restart completes. (#10224)$$$$$$Dynamic ports for the Cluster Dashboard$$$The Cluster Dashboards API server used to bind to a fixed port (9443) and failed to start when another program already used it. It now picks an available port automatically at startup. (#1890)$$$$$$Windows: proxy bypass for domains and wildcards$$$The no-proxy list now supports domain names and wildcard patterns (e.g. *.example.com) in addition to IP addresses and CIDR subnets. (#9803)$$$$$$AI Workbench extension$$$The bundled Open WebUI extension has been renamed to AI Workbench and updated to version 0.2.0. AI Workbench provides a local web interface for interacting with large language models running in containers; letting you experiment with AI workloads directly from Rancher Desktop.$$$$$$Installed extension details$$$Thanks to @officialasishkumar; the Installed extensions table now shows each extensions vendor; description; and a More information link; drawn from the metadata the extension already publishes. (#8698)$$$$$$Improved macOS disk image installer$$$Thanks to @maximumschmidt; the macOS disk image now guides installation: a lasso wraps the Rancher Desktop icon and points it toward the Applications folder; under a Drag to Applications to install instruction. The Finder volume title reads Install Rancher Desktop … so it names the action rather than the product. (#10194)$$$$$$Bug Fixes$$$macOS and Linux: could fail to start after an unclean shutdown$$$After an unclean shutdown; such as a host crash or force-quit; Rancher Desktop could refuse to start because a leftover virtual-machine process confused its startup checks. Rancher Desktop now clears the leftover process and starts normally. (#7760)$$$$$$Windows: startup could fail after many launches$$$After Rancher Desktop had been started many times; it could stop starting altogether: each launch added a certificate to the VMs trust store — once that store filled past a fixed limit; certificate setup failed and blocked startup. Rancher Desktop now removes stale certificates before adding new ones. Thanks to @cm-iwata! (#9929)$$$$$$Windows: running other-architecture binaries could stop working$$$Starting Rancher Desktop could disable support for running binaries built for other architectures (WSLInterop) — not only inside Rancher Desktop; but in your other WSL distributions too. Rancher Desktop now leaves those registrations alone. (#10049)$$$$$$Windows: host-network containers could shadow published ports$$$A container run with --network=host and listening on 127.0.0.1 could hijack a port that another container had published with -p; or that a Kubernetes hostPort used — leaving the published port unreachable fr

**File not scanned for virus due to size.**$$$$$$Release Notes for 1.22.3$$$Rancher Desktop 1.22.3 is a security-focused patch release. We strongly recommend upgrading.$$$$$$Security Fixes$$$Important$$$$$$macOS and Linux: additional steps required after upgrading.$$$A bug in the ISO version comparison means an in-place upgrade from any earlier 1.22.x release will keep booting the previous kernel; leaving the modules listed below in place. Choose one of these to apply the container-escape mitigation:$$$$$$Manual kernel upgrade (preserves your data): follow the steps in #10288.$$$Factory reset: run Troubleshooting ? Factory Reset after upgrading. This removes all containers; images; and Kubernetes state — back up anything you need to keep first.$$$Windows is not affected: the mitigation ships in the application binary and applies on the next start.$$$$$$Container escape mitigation (CVE-2026-31431; CVE-2026-43284; CVE-2026-43500)$$$Three recent Linux kernel exploits — copy.fail (CVE-2026-31431) and the two dirtyfrag variants (CVE-2026-43284; CVE-2026-43500) — let unprivileged processes gain a page-cache write primitive and tamper with files outside their normal reach. Inside Rancher Desktop; that means an attacker with code execution in any container could escape that scope and modify the rest of the VM.$$$$$$Each exploit needs a specific Linux kernel module loaded. Rancher Desktop now removes those modules; so the exploits have nothing to hook into.

**File not scanned for virus due to size.**$$$$$$Release Notes for 1.22.3$$$Rancher Desktop 1.22.3 is a security-focused patch release. We strongly recommend upgrading.$$$$$$Security Fixes$$$Important$$$$$$macOS and Linux: additional steps required after upgrading.$$$A bug in the ISO version comparison means an in-place upgrade from any earlier 1.22.x release will keep booting the previous kernel; leaving the modules listed below in place. Choose one of these to apply the container-escape mitigation:$$$$$$Manual kernel upgrade (preserves your data): follow the steps in #10288.$$$Factory reset: run Troubleshooting ? Factory Reset after upgrading. This removes all containers; images; and Kubernetes state — back up anything you need to keep first.$$$Windows is not affected: the mitigation ships in the application binary and applies on the next start.$$$$$$Container escape mitigation (CVE-2026-31431; CVE-2026-43284; CVE-2026-43500)$$$Three recent Linux kernel exploits — copy.fail (CVE-2026-31431) and the two dirtyfrag variants (CVE-2026-43284; CVE-2026-43500) — let unprivileged processes gain a page-cache write primitive and tamper with files outside their normal reach. Inside Rancher Desktop; that means an attacker with code execution in any container could escape that scope and modify the rest of the VM.$$$$$$Each exploit needs a specific Linux kernel module loaded. Rancher Desktop now removes those modules; so the exploits have nothing to hook into.

**File not scanned for virus due to size.**$$$$$$Release Notes for 1.22.0$$$Whats New$$$Select moby storage driver$$$Version 1.21.0 switched to the containerd-snapshotter storage driver by default. On Windows; this happened unconditionally (even on upgrades); which made existing images inaccessible.$$$$$$Users can now choose between the classic and containerd-snapshotter storage drivers via rdctl:$$$$$$rdctl set --container-engine.moby-storage-driver classic$$$rdctl set --container-engine.moby-storage-driver snapshotter$$$Rancher Desktop automatically selects the driver based on where your existing images are stored. See Migrating Images for instructions on moving images between storage drivers. Windows users affected by the 1.21.0 issue can switch back to the classic driver to regain access to their images. (#9732)

**File not scanned for virus due to size.**$$$$$$Release Notes for 1.22.0$$$Whats New$$$Select moby storage driver$$$Version 1.21.0 switched to the containerd-snapshotter storage driver by default. On Windows; this happened unconditionally (even on upgrades); which made existing images inaccessible.$$$$$$Users can now choose between the classic and containerd-snapshotter storage drivers via rdctl:$$$$$$rdctl set --container-engine.moby-storage-driver classic$$$rdctl set --container-engine.moby-storage-driver snapshotter$$$Rancher Desktop automatically selects the driver based on where your existing images are stored. See Migrating Images for instructions on moving images between storage drivers. Windows users affected by the 1.21.0 issue can switch back to the classic driver to regain access to their images. (#9732)

**File not scanned for virus due to size.**$$$$$$Release Notes for 1.22.0$$$Whats New$$$Select moby storage driver$$$Version 1.21.0 switched to the containerd-snapshotter storage driver by default. On Windows; this happened unconditionally (even on upgrades); which made existing images inaccessible.$$$$$$Users can now choose between the classic and containerd-snapshotter storage drivers via rdctl:$$$$$$rdctl set --container-engine.moby-storage-driver classic$$$rdctl set --container-engine.moby-storage-driver snapshotter$$$Rancher Desktop automatically selects the driver based on where your existing images are stored. See Migrating Images for instructions on moving images between storage drivers. Windows users affected by the 1.21.0 issue can switch back to the classic driver to regain access to their images. (#9732)