Rancher Desktop: baixar versions anteriors

This is the 1.23.1 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
• Windows
• macOS x86_64
• macOS aarch64
• Linux install notes
Rancher Desktop 2.0 Alpha 1 is available
The first alpha of Rancher Desktop 2.0 is out：a ground-up rewrite that runs with or without the GUI and installs alongside Rancher Desktop without touching it. It is an early tech preview, not for production. For what it is and how to try it, see Welcome to Rancher Desktop 2.0 on our blog.
New Contributors
Thank you to our new contributors：@linghengqian, @endemics, @cm-iwata, @maximumschmidt, @immanuwell, @officialasishkumar, and @edwinbalani!
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.
Release Notes for 1.23.0
What's 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 Dashboard's 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 extension's 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 

This is the 1.23.1 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Rancher Desktop 2.0 Alpha 1 is available
The first alpha of Rancher Desktop 2.0 is out: a ground-up rewrite that runs with or without the GUI and installs alongside Rancher Desktop without touching it. It is an early tech preview, not for production. For what it is and how to try it, see Welcome to Rancher Desktop 2.0 on our blog.
New Contributors
Thank you to our new contributors: @linghengqian, @endemics, @cm-iwata, @maximumschmidt, @immanuwell, @officialasishkumar, and @edwinbalani!
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.
Release Notes for 1.23.0
What's 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 Dashboard's 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 extension's 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

This is the 1.23.0 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Rancher Desktop 2.0 Alpha 1 is available
The first alpha of Rancher Desktop 2.0 is out: a ground-up rewrite that runs with or without the GUI and installs alongside Rancher Desktop without touching it. It is an early tech preview, not for production. For what it is and how to try it, see Welcome to Rancher Desktop 2.0 on our blog.
New Contributors
Thank you to our new contributors: @linghengqian, @endemics, @cm-iwata, @maximumschmidt, @immanuwell, @officialasishkumar, and @edwinbalani!
Release Notes for 1.23.0
What's 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 Dashboard's 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 extension's 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 VM's 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 o

This is the 1.22.3 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Release Notes for 1.22.3
Rancher Desktop 1.22.3 is a security-focused patch release. We strongly recommend upgrading.
Security Fixes
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.
Modules removed:
──────────┬──────────────────────────────────────────────────────────────────────────┬─────────────────────────────────────────
Module │Used for │CVE it enables
──────────┼──────────────────────────────────────────────────────────────────────────┼─────────────────────────────────────────
esp4 / │IPsec ESP (site-to-site VPN gateways, e.g. strongSwan, libreswan) │CVE-2026-43284 (dirtyfrag, XFRM ESP)
esp6 │ │
──────────┼──────────────────────────────────────────────────────────────────────────┼─────────────────────────────────────────
rxrpc │RxRPC protocol, used almost exclusively by AFS / kAFS (Andrew File System)│CVE-2026-43500 (dirtyfrag, AF_RXRPC)
──────────┼──────────────────────────────────────────────────────────────────────────┼─────────────────────────────────────────
algif_aead│Kernel AEAD crypto via AF_ALG sockets (offload to hardware accelerators) │CVE-2026-31431 (copy.fail)
──────────┴──────────────────────────────────────────────────────────────────────────┴─────────────────────────────────────────
What this means for you: unless you run an IPsec VPN endpoint or an AFS client, the removal is invisible to you.
On macOS and Linux, the rebuilt Alpine VM image omits the modules. (#10220, #10248)
On Windows, WSL2 provides kernel modules through a single overlay shared by every WSL distro running on the host, which means:
- When Rancher Desktop starts, it removes these modules for all running WSL distros, not just its own. Other distros will lose IPsec ESP, AFS, and AF_ALG until WSL itself restarts.
- When WSL restarts (e.g. wsl --shutdown followed by launching any distro), the upstream WSL kernel restores the modules.
- The next time Rancher Desktop starts, it removes them again.
This is an "apply-on-start" / "forget-on-stop" lifecycle: Rancher Desktop never persists changes to your WSL installation. (#10247)
The bundled Alpine VM image also picks up a newer kernel containing additional upstream security patches.
Bug Fixes
Bind mounts via the Docker --mount flag on Windows
In Rancher Desktop 1.22.2, docker run --mount type=bind,... on Windows could mount the wrong directory or fail to start the container. This release restores correct bind-mount behavior; the -v /path:/path shorthand stayed correct throughout. (#10252)
Release Notes for 1.22.2
Rancher Desktop 1.22.2 is a patch release fixing a critical bug on macOS (and maybe on Linux). It contains no further changes beyond the following 2 items:
Fixed data volume mount on macOS
Under certain conditions, the data volume failed to mount on macOS. In that case, all data was stored in a RAM disk, which is limited to the amount of memory allocated to the VM (usually 6GB). This resulted in early out-of-memory errors when building or pulling images.
When Rancher Desktop was restarted, all data from the current session was lost because it was never written to disk. Theoretically, this could also have happened on Linux, but it has only been reported in macOS (#9754 and #10133)
Upgrade trivy 0.68.2 → 0.70.0
This upgr

This is the 1.22.0 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Release Notes for 1.22.0
What's 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 --experimental.container-engine.docker.storage-driver classic
rdctl set --experimental.container-engine.docker.storage-driver containerd-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)
Docker 29 in the VM
Alpine Linux has been updated to version 3.23, which includes Docker 29. This fixes issues with docker inspect returning incomplete image metadata. (#9671, #9739)
Kubernetes Dashboard improvements
Pod log streaming now works in the Dashboard. This was broken since version 1.6.0. (#3212)
The Dashboard button now waits until the Steve API server accepts connections before becoming active. Previously, clicking the button too quickly after Kubernetes started would show a spinner that never resolved. (#8217)
The non-functional "Download KubeConfig" and "Kubectl Shell" buttons have been removed from the cluster dashboard. (#2208, #8151, #8757)
Docker Compose 5.0
Docker Compose has been updated to version 5.0. Key changes include:
- Compose can now be used as an SDK for third-party integrations
- The internal builder has been removed; builds are delegated to Docker Bake
- Hooks now run on restart
- New --wait option for the start command
Helm 4.0
Helm has been updated to version 4.0. See the Helm 4.0 release notes for details on the changes.
Diagnostics
Moby image store check
A new diagnostic reports when images exist in the inactive image store (classic vs. containerd-snapshotter), helping identify which images need migration. (#9733)
Windows: wsl-vpnkit detection
A new diagnostic warns when the wsl-vpnkit distribution is present, as it can cause networking issues with Rancher Desktop. (#9623)
Bug Fixes
macOS CA management with multiple keychains
Fixed a bug where certificates from multiple keychains were being written to the same file path, causing only the last keychain's certificates to be processed. (#9755)
K3s version channel labels not updating
Fixed an issue where version channel labels (e.g, stable, latest, v1.xx) were not removed from old versions when they moved to newer versions, causing multiple patch versions to appear in the recommended list. (#9709)
K3s image loading for older versions
Made the --all-platforms flag optional when loading K3s images, so older K3s versions (before 1.31) load images correctly. (#9708, #9710)
rdctl info works after upgrade
Fixed an issue where rdctl info failed with a BusyBox error for users who upgraded from version 1.19.3 or earlier, or restored an old snapshot. The 1.21.0 release notes mentioned a manual workaround; this is no longer needed. (#9546, #9554)
Containers page error handling
Fixed an "[object Object]" error that appeared on the Containers page when the backend became temporarily unavailable. (#9545, #9661)
Connectivity check uses HTTPS
The network connectivity diagnostic now uses an HTTPS HEAD request instead of HTTP GET, improving privacy by encrypting the request. (#9711)
Linux packaging fixes
Fixed an issue where the Debian package did not set the suid bit on chrome-sandbox, causing the application to fail to start on Debian and Ubuntu systems.
The virtualization support check now works correctly on Linux arm64 systems.
Extension fixes
Fixe

This is the 1.21.0 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Release Notes for 1.21.0
What's New
rdctl info command
rdctl has a new info command that lists the Rancher Desktop version and the IP address of the VM:
❯ rdctl info
Version: v1.21.0
IPAddress: 192.168.205.2
You can query individual fields for use in scripts:
❯ rdctl info --field ip-address
192.168.205.2
Increasing disk size (Linux and macOS)
Rancher Desktop by default reserves 100GB of disk space for the VM (it is a sparse file, so only the portion in use actually takes up disk space on the host).
It is now possible to increase the maximum size of the VM disk using rdctl:
❯ rdctl set --experimental.virtual-machine.disk-size 120G
Status: reconfiguring Rancher Desktop to apply changes (this may take a while).
This will restart Rancher Desktop, at which time the volume will expand to the larger size. Please note that it is not possible to reduce the maximum size. Unused space in the VM disk will be returned for host usage every time Rancher Desktop is restarted (via fstrim).
There is no GUI mechanism to change the maximum disk size.
Update checker only checks once a day
Rancher Desktop will only check for updates once per day now instead of every hour. This interval is not configurable but the update checks can be disabled completely via both rdctl and the GUI.
Online checker frequency is configurable
By default, Rancher Desktop checks every 5 seconds to update the "online" indicator. It does this by checking for the right redirect response from http://docs.rancherdesktop.io (to https). This also detects when the computer is caught inside a captive portal, like airport or hotel wifi.
You can now change the frequency of this check to a longer value (in milliseconds) or disable it completely by setting it to 0:
❯ rdctl set --diagnostics.connectivity.interval 0
Status: settings updated; no restart required.
Electron will still perform its own online checks (which will also update the Rancher Desktop indicators) but those checks are somewhat unreliable.
There is no mechanism in the GUI to change this setting.
Container Info page with logs
@tylercritchlow has moved the container logs to a container info page. You get to the info page either by clicking the container name or through the menu at the end of the line.
moby now uses containerd snapshotter by default
On new installations, or after a factory reset, Rancher Desktop will now use the containerd snapshotter for storing container images by default. This snapshotter provides additional functionality, such as storing/pushing/pulling multi-platform images. It is also needed for using Wasm containers with docker. This means Rancher Desktop will no longer switch between snapshotters when turning Wasm support on or off, so local images will remain visible to both configuration options.
Updated extensions
The "SUSE Application Collection" extension can now display the collection without having to log in first.
Bug fixes
UDP port forwarding fixed on Linux and macOS
It was already working on Windows. Thanks to @toshs for finding and fixing the issue.
Shadows on macOS 26 Tahoe
Window shadows had a performance issue on macOS 26. This has been fixed by upgrading the Electron version.
Updates to Bundled Utilities (from Rancher Desktop 1.20.1, as of 1.21.0)
- amazon-ecr-credential-helper 0.10.1 → 0.11.0
- docker 28.3.3 → 29.0.2
- docker-buildx 0.26.1 → 0.30.1
- docker-compose 2.39.2 → 2.40.3
- docker-credential-helpers 0.9.3 → 0.9.4
- helm 3.18.6 → 3.19.1
- kuberlr unchanged 0.6.1
- moby/buildkit 0.21.1 → 0.25.2
- nerdctl 2.1.3 → 2.2.0
- spin 3.3.1 → 3.5.1
- spin-shim 0.20.0 → 0.22.0
- spin-operator unchanged 0.6.1
- trivy 0.65.0 → 0.67.2
Connect with the developers
- The issue queue
- Rancher Users Slack in the #rancher-desktop channel
Changelog
The full version ch

This is the 1.20.1 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Release Notes for 1.20.1
This release updates the bundled docker-compose from version 2.39.2 to 2.40.3 to address CVE-2025-62725.
There are no other changes in this patch release.
New Contributors
Thank you to our new contributors: @proski, @lavigneer, and @tylercritchlow!
Release Notes for 1.20.0
What's New
Container Logs
Thanks to @tylercritchlow, the Containers dashboard can now display the container logs. The Logs command is accessible under the ⋮ menu on the right hand side, so it's a bit hidden. This will automatically scroll to the end of the log and it updates automatically as more logs come in.
Container Dashboard Improvements
@tylercritchlow has also made changes to the Containers dashboard itself: it will now automatically update as containers are created, started, stopped or deleted. You no longer need to refresh manually.
As well, containers are now grouped together, either by Kubernetes pod, by docker-compose deployment or in the "Standalone Containers" group for everything else. Groups can individually be collapsed and expanded.
New Volumes page
Another new feature thanks to @tylercritchlow: On the Volumes page, you can see a list of all volumes managed by the container runtime and, if required, delete volumes.
New rdctl reset command
@lavigneer has contributed the new rdctl reset command. It is a refinement of the rdctl factory-reset command, which is still supported, but now deprecated and hidden. It adds the ability to delete the Kubernetes version cache, which was previously only possible from within the GUI.
─────────────────────┬───────────────────────────────────────────────────
Command │Function
─────────────────────┼───────────────────────────────────────────────────
rdctl reset --vm │deletes VM and creates a new with the same settings
─────────────────────┼───────────────────────────────────────────────────
rdctl reset --k8s │deletes deployed Kubernetes workloads
─────────────────────┼───────────────────────────────────────────────────
rdctl reset --cache │deletes cached Kubernetes images
─────────────────────┼───────────────────────────────────────────────────
rdctl reset --factory│deletes VM and shows first-start dialog again
─────────────────────┴───────────────────────────────────────────────────
All options can be combined but some combinations are redundant:
- --factory includes --vm and k8s (but not --cache)
- --vm includes --k8s
VZ emulation mode is now the default on macOS
On a fresh install, or after a factory reset, the default emulation mode on macOS is now VZ instead of QEMU.
The default mount type with VZ is now virtiofs, which is no longer considered "experimental".
Additional locations for system deployment profiles
On macOS, Rancher Desktop will check for system deployment profiles first in /Library/Managed Preferences. If no profile is found there, then it looks in the previous default location at /Library/Preferences. This allows deploying system profiles using MDM solutions.
On Linux, Rancher Desktop continues to look in /etc/rancher-desktop first. But if no profile is found there, it will now also check /usr/etc/rancher-desktop for a system profile before looking in the user profile location.
Additional Diagnostics
When using the moby container engine, Rancher Desktop will now run diagnostics checks to verify that the current docker context is rancher-desktop and that DOCKER_HOST is not set.
On Windows, there is also a new diagnostic that will trigger when the WSL2 version is too old.
Updated extensions
The extension catalog now lists the latest releases of "Epinio", "Open WebUI" and the "SUSE Application Collection".
The "Open WebUI" extension no longer binds to a specific version, but will always attempt to fetch the latest release when it is being rest

This is the 1.20.0 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
New Contributors
Thank you to our new contributors: @proski, @lavigneer, and @tylercritchlow!
Release Notes for 1.20.0
What's New
Container Logs
Thanks to @tylercritchlow, the Containers dashboard can now display the container logs. The Logs command is accessible under the ⋮ menu on the right hand side, so it's a bit hidden. This will automatically scroll to the end of the log and it updates automatically as more logs come in.
Container Dashboard Improvements
@tylercritchlow has also made changes to the Containers dashboard itself: it will now automatically update as containers are created, started, stopped or deleted. You no longer need to refresh manually.
As well, containers are now grouped together, either by Kubernetes pod, by docker-compose deployment or in the "Standalone Containers" group for everything else. Groups can individually be collapsed and expanded.
New Volumes page
Another new feature thanks to @tylercritchlow: On the Volumes page, you can see a list of all volumes managed by the container runtime and, if required, delete volumes.
New rdctl reset command
@lavigneer has contributed the new rdctl reset command. It is a refinement of the rdctl factory-reset command, which is still supported, but now deprecated and hidden. It adds the ability to delete the Kubernetes version cache, which was previously only possible from within the GUI.
─────────────────────┬───────────────────────────────────────────────────
Command │Function
─────────────────────┼───────────────────────────────────────────────────
rdctl reset --vm │deletes VM and creates a new with the same settings
─────────────────────┼───────────────────────────────────────────────────
rdctl reset --k8s │deletes deployed Kubernetes workloads
─────────────────────┼───────────────────────────────────────────────────
rdctl reset --cache │deletes cached Kubernetes images
─────────────────────┼───────────────────────────────────────────────────
rdctl reset --factory│deletes VM and shows first-start dialog again
─────────────────────┴───────────────────────────────────────────────────
All options can be combined but some combinations are redundant:
- --factory includes --vm and k8s (but not --cache)
- --vm includes --k8s
VZ emulation mode is now the default on macOS
On a fresh install, or after a factory reset, the default emulation mode on macOS is now VZ instead of QEMU.
The default mount type with VZ is now virtiofs, which is no longer considered "experimental".
Additional locations for system deployment profiles
On macOS, Rancher Desktop will check for system deployment profiles first in /Library/Managed Preferences. If no profile is found there, then it looks in the previous default location at /Library/Preferences. This allows deploying system profiles using MDM solutions.
On Linux, Rancher Desktop continues to look in /etc/rancher-desktop first. But if no profile is found there, it will now also check /usr/etc/rancher-desktop for a system profile before looking in the user profile location.
Additional Diagnostics
When using the moby container engine, Rancher Desktop will now run diagnostics checks to verify that the current docker context is rancher-desktop and that DOCKER_HOST is not set.
On Windows, there is also a new diagnostic that will trigger when the WSL2 version is too old.
Updated extensions
The extension catalog now lists the latest releases of "Epinio", "Open WebUI" and the "SUSE Application Collection".
The "Open WebUI" extension no longer binds to a specific version, but will always attempt to fetch the latest release when it is being restarted.
Vue.JS has been upgraded from Vue2 → Vue3
The Vue JavaScript framework has been updated to the latest version, which required a rather large amount of internal changes. Idea

This is the 1.19.3 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Release Notes for 1.19.3
AppImage release works again
An update to one of our dependencies broke the AppImage releases. This has been fixed.
Upgraded bundled utilities
The following utilities have been updated:
- docker-buildx 0.24.0 → 0.25.0
- helm 3.18.0 → 3.18.3
- spin 3.3.0 → 3.3.1
Release Notes for 1.19.2
Images built with OpenJDK 17 to 24 no longer crash (Linux and macOS)
OpenJDK releases 17 to 24 cannot properly detect the cgroup version when running on a Linux kernel 6.12+. Rancher Desktop 1.19.2 downgrades the bundled Linux kernel to version 6.6; this allows more time for images to be rebuilt once the fixed OpenJDK 25 is released.
VZ emulation with Rosetta works on earlier macOS releases than 15.5
As a side-effect of downgrading the kernel, VZ emulation with Rosetta will work again on older macOS releases.
The spin up command works again (macOS)
In Rancher Desktop 1.17.0, the spin binary was moved to a different location and no longer signed with the required entitlements on macOS, causing it to fail code compiled into executable memory. This has been fixed.
Upgraded bundled utilities
The following utilities have been updated:
- docker-compose 2.36.2 → 2.37.1
- spin 3.2.0 → 3.3.0
Release Notes for 1.19.1
VZ emulation with Rosetta requires macOS 15.5
Older Rosetta releases are incompatible with the latest Linux kernel releases (6.11 and later). Rancher Desktop 1.19 uses a Linux 6.12.28 kernel on Linux and macOS and requires the updated Rosetta version from macOS 15.5 or later. This is only a concern for running amd64 container images on Apple silicon machines.
Gnome Desktop compatibility
The 1.19.0 release did not run on Linux with Gnome Desktop. This has been fixed.
SUSE Application Collection extension upgraded to 0.2.2.
The extension had a new release with a few bug fixes.
Release Notes for 1.19.0
What's New
Extension update mechanism
The "Extensions" menu item on the left will show a red bubble with a count of all installed extensions that have an update available from the built-in catalog. The cards for those extensions will have an "Update" button in addition to the "Remove" button.
SUSE Application Collection extension
SUSE Application Collection gives access to trusted, curated, and continuously updated applications. This extension helps you integrate the collection into your local development environment by managing authentication, making apps plug-and-play, and helping you stay up-to-date.
Epinio extension is working again
Thanks to the team at Krumware for taking over maintenance of the Epinio extension! (#6580 and #7280)
Open WebUI extension has MCP support
This update adds a simple, secure MCP-to-OpenAPI proxy server running in a container. It provides access to tools using the Model Context Protocol from the LLM.
It comes pre-configured with a docker and a kubernetes MCP server implementation, allowing the model to talk to the local Moby engine or Kubernetes cluster.
VZ emulation and Snapshots are no longer experimental
The --experimental.virtual-machine.type and --experimental.virtual-machine.use-rosetta options in rdctl are now just --virtual-machine.type and --virtual-machine.use-rosetta.
Bug fixes
Kubernetes reset no longer breaks on Windows
When using Kubernetes 1.30.0 or later, a "Kubernetes Reset" would leave Rancher Desktop in a broken state until WSL2 was restarted (or the host rebooted) #8648.
QEMU slow image pulling (on Linux and macOS) has been fixed
The root cause has been a delay in the DNS host resolver implementation (#4258).
Extensions (on macOS) can now call bundled utilities
Extensions were unable to use bundled utilities such as the credential helpers because Rancher Desktop is normally launched by the Finder and does not inherit the user's PATH setting. With

This is the 1.19.2 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Release Notes for 1.19.2
Images built with OpenJDK 17 to 24 no longer crash (Linux and macOS)
OpenJDK releases 17 to 24 cannot properly detect the cgroup version when running on a Linux kernel 6.12+. Rancher Desktop 1.19.2 downgrades the bundled Linux kernel to version 6.6; this allows more time for images to be rebuilt once the fixed OpenJDK 25 is released.
VZ emulation with Rosetta works on earlier macOS releases than 15.5
As a side-effect of downgrading the kernel, VZ emulation with Rosetta will work again on older macOS releases.
The spin up command works again (macOS)
In Rancher Desktop 1.17.0, the spin binary was moved to a different location and no longer signed with the required entitlements on macOS, causing it to fail code compiled into executable memory. This has been fixed.
Upgraded bundled utilities
The following utilities have been updated:
- docker-compose 2.36.2 → 2.37.1
- spin 3.2.0 → 3.3.0
Release Notes for 1.19.1
VZ emulation with Rosetta requires macOS 15.5
Older Rosetta releases are incompatible with the latest Linux kernel releases (6.11 and later). Rancher Desktop 1.19 uses a Linux 6.12.28 kernel on Linux and macOS and requires the updated Rosetta version from macOS 15.5 or later. This is only a concern for running amd64 container images on Apple silicon machines.
Gnome Desktop compatibility
The 1.19.0 release did not run on Linux with Gnome Desktop. This has been fixed.
SUSE Application Collection extension upgraded to 0.2.2.
The extension had a new release with a few bug fixes.
Release Notes for 1.19.0
What's New
Extension update mechanism
The "Extensions" menu item on the left will show a red bubble with a count of all installed extensions that have an update available from the built-in catalog. The cards for those extensions will have an "Update" button in addition to the "Remove" button.
SUSE Application Collection extension
SUSE Application Collection gives access to trusted, curated, and continuously updated applications. This extension helps you integrate the collection into your local development environment by managing authentication, making apps plug-and-play, and helping you stay up-to-date.
Epinio extension is working again
Thanks to the team at Krumware for taking over maintenance of the Epinio extension! (#6580 and #7280)
Open WebUI extension has MCP support
This update adds a simple, secure MCP-to-OpenAPI proxy server running in a container. It provides access to tools using the Model Context Protocol from the LLM.
It comes pre-configured with a docker and a kubernetes MCP server implementation, allowing the model to talk to the local Moby engine or Kubernetes cluster.
VZ emulation and Snapshots are no longer experimental
The --experimental.virtual-machine.type and --experimental.virtual-machine.use-rosetta options in rdctl are now just --virtual-machine.type and --virtual-machine.use-rosetta.
Bug fixes
Kubernetes reset no longer breaks on Windows
When using Kubernetes 1.30.0 or later, a "Kubernetes Reset" would leave Rancher Desktop in a broken state until WSL2 was restarted (or the host rebooted) #8648.
QEMU slow image pulling (on Linux and macOS) has been fixed
The root cause has been a delay in the DNS host resolver implementation (#4258).
Extensions (on macOS) can now call bundled utilities
Extensions were unable to use bundled utilities such as the credential helpers because Rancher Desktop is normally launched by the Finder and does not inherit the user's PATH setting. With this release, the directory with bundled utilities will be added explicitly when an extension invokes external programs (#8598).
docker build on Windows no longer fails intermittently with http2 errors
This was a regression in Rancher Desktop 1.18.* on Windows only due to a buffering i

This is the 1.19.1 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Release Notes for 1.19.1
Gnome Desktop compatibility
The 1.19.0 release did not run on Linux with Gnome Desktop. This has been fixed.
SUSE Application Collection extension upgraded to 0.2.2.
The extension had a new release with a few bug fixes.
Release Notes for 1.19.0
What's New
Extension update mechanism
The "Extensions" menu item on the left will show a red bubble with a count of all installed extensions that have an update available from the built-in catalog. The cards for those extensions will have an "Update" button in addition to the "Remove" button.
SUSE Application Collection extension
SUSE Application Collection gives access to trusted, curated, and continuously updated applications. This extension helps you integrate the collection into your local development environment by managing authentication, making apps plug-and-play, and helping you stay up-to-date.
Epinio extension is working again
Thanks to the team at Krumware for taking over maintenance of the Epinio extension! (#6580 and #7280)
Open WebUI extension has MCP support
This update adds a simple, secure MCP-to-OpenAPI proxy server running in a container. It provides access to tools using the Model Context Protocol from the LLM.
It comes pre-configured with a docker and a kubernetes MCP server implementation, allowing the model to talk to the local Moby engine or Kubernetes cluster.
VZ emulation and Snapshots are no longer experimental
The --experimental.virtual-machine.type and --experimental.virtual-machine.use-rosetta options in rdctl are now just --virtual-machine.type and --virtual-machine.use-rosetta.
Bug fixes
Kubernetes reset no longer breaks on Windows
When using Kubernetes 1.30.0 or later, a "Kubernetes Reset" would leave Rancher Desktop in a broken state until WSL2 was restarted (or the host rebooted) #8648.
QEMU slow image pulling (on Linux and macOS) has been fixed
The root cause has been a delay in the DNS host resolver implementation (#4258).
Extensions (on macOS) can now call bundled utilities
Extensions were unable to use bundled utilities such as the credential helpers because Rancher Desktop is normally launched by the Finder and does not inherit the user's PATH setting. With this release, the directory with bundled utilities will be added explicitly when an extension invokes external programs (#8598).
docker build on Windows no longer fails intermittently with http2 errors
This was a regression in Rancher Desktop 1.18.* on Windows only due to a buffering issue in the proxy implementation (#8276).
Many thanks to @bcxpro for analyzing the failure and providing a fix! (#8311)
nerdctl on Windows can now use alternate filenames for Dockerfile
This was a bug in the argument translation layer in nerdctl-stub (#8190).
Updates to Bundled Utilities
- amazon-eco-credential-helper unchanged 0.9.1
- docker 27.5.1 → 28.1.1
- docker-buildx 0.20.1 → 0.24.0
- docker-compose 2.33.0 → 2.36.2
- docker-credential-helpers 0.8.2 → 0.9.3
- helm 3.17.1 → 3.18.0
- kuberlr 0.5.2 → 0.6.0
- moby/buildkit 0.19.0 → 0.21.1
- nerdctl 2.0.3 → 2.1.1
- spin 3.1.2 → 3.2.0
- spin-shim 0.18.0 → 0.19.0
- spinkube unchanged 0.4.0
- trivy 0.59.1 → 0.62.1
Connect with the developers
- The issue queue
- Rancher Users Slack in the #rancher-desktop channel
Changelog
The full version changelog, from v1.18.0, can be found using GitHub compare and the details of the release can be found in the v1.19.0 milestone.

This is the 1.19.0 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Release Notes for 1.19.0
What's New
Extension update mechanism
The "Extensions" menu item on the left will show a red bubble with a count of all installed extensions that have an update available from the built-in catalog. The cards for those extensions will have an "Update" button in addition to the "Remove" button.
SUSE Application Collection extension
SUSE Application Collection gives access to trusted, curated, and continuously updated applications. This extension helps you integrate the collection into your local development environment by managing authentication, making apps plug-and-play, and helping you stay up-to-date.
Epinio extension is working again
Thanks to the team at Krumware for taking over maintenance of the Epinio extension! (#6580 and #7280)
Open WebUI extension has MCP support
This update adds a simple, secure MCP-to-OpenAPI proxy server running in a container. It provides access to tools using the Model Context Protocol from the LLM.
It comes pre-configured with a docker and a kubernetes MCP server implementation, allowing the model to talk to the local Moby engine or Kubernetes cluster.
VZ emulation and Snapshots are no longer experimental
The --experimental.virtual-machine.type and --experimental.virtual-machine.use-rosetta options in rdctl are now just --virtual-machine.type and --virtual-machine.use-rosetta.
Bug fixes
Kubernetes reset no longer breaks on Windows
When using Kubernetes 1.30.0 or later, a "Kubernetes Reset" would leave Rancher Desktop in a broken state until WSL2 was restarted (or the host rebooted) #8648.
QEMU slow image pulling (on Linux and macOS) has been fixed
The root cause has been a delay in the DNS host resolver implementation (#4258).
Extensions (on macOS) can now call bundled utilities
Extensions were unable to use bundled utilities such as the credential helpers because Rancher Desktop is normally launched by the Finder and does not inherit the user's PATH setting. With this release, the directory with bundled utilities will be added explicitly when an extension invokes external programs (#8598).
docker build on Windows no longer fails intermittently with http2 errors
This was a regression in Rancher Desktop 1.18.* on Windows only due to a buffering issue in the proxy implementation (#8276).
Many thanks to @bcxpro for analyzing the failure and providing a fix! (#8311)
nerdctl on Windows can now use alternate filenames for Dockerfile
This was a bug in the argument translation layer in nerdctl-stub (#8190).
Updates to Bundled Utilities
- amazon-eco-credential-helper unchanged 0.9.1
- docker 27.5.1 → 28.1.1
- docker-buildx 0.20.1 → 0.24.0
- docker-compose 2.33.0 → 2.36.2
- docker-credential-helpers 0.8.2 → 0.9.3
- helm 3.17.1 → 3.18.0
- kuberlr 0.5.2 → 0.6.0
- moby/buildkit 0.19.0 → 0.21.1
- nerdctl 2.0.3 → 2.1.1
- spin 3.1.2 → 3.2.0
- spin-shim 0.18.0 → 0.19.0
- spinkube unchanged 0.4.0
- trivy 0.59.1 → 0.62.1
Connect with the developers
- The issue queue
- Rancher Users Slack in the #rancher-desktop channel
Changelog
The full version changelog, from v1.18.0, can be found using GitHub compare and the details of the release can be found in the v1.19.0 milestone.

This is the 1.18.2 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
What has changed in 1.18.2
Windows regression with docker-proxy has been fixed
Rancher Desktop 1.18.0 includes a fix for docker run commands on Windows that unfortunately introduced a race condition that sometimes breaks the communication between the docker.exe command and the docker daemon, resulting in http2 errors (#8276). Thanks to @bcxpro for providing a fix (#8311)!
Open WebUI extension has been updated to fix Ollama installation on Linux and macOS
If Ollama is not already installed on the system, then the extension will download and install Ollama just inside the extension directory. This had been broken by a change to the upstream Linux and macOS release formats. It does not affect users that already have Ollama installed because in that case the extension will just use the installed version.
The version of Open WebUI has been updated to 0.5.20.
Please note: there was no public release of 1.18.1
An issue with the Open WebUI extension was found after the 1.18.1 tag was already created, so this version had to be skipped.
Release Notes for 1.18.0
Cluster dashboard has been updated from 2.7.0 to 2.11.0
The cluster dashboard has been reimplemented as a Rancher extension and is mostly in sync with the upstream version.
The dashboard now works correctly even when the KUBECONFIG environment variable points to multiple config files.
Network fixes
The gvisor-tap-vsock dependency has been updated again, which has solved several networking regressions from Rancher Desktop 1.17.x (on all platforms).
Rancher Desktop is working properly again when behind a VPN. On macOS the VZ emulation mode works again even without a network connection.
Image scanning now scans local images with containerd
This already worked before for moby.
Image scanning results are displayed much faster once the vulnerability databases have been downloaded (for images with many vulnerabilities).
The Open WebUI extension has been updated
If you already have the extension installed, then you must uninstall it from the "Installed" tab of the "Extensions" page (the "Remove" button on the "Catalog" tab does not work correctly in this release).
After you have uninstalled the current version, you can install the new version as usual from the "Catalog" tab.
docker run issues on Windows have been fixed
docker run on Windows would hang indefinitely when reading from STDIN (#2094) or would produce no output when running without the -i option (#3239). Many thanks to @bcxpro for investigating and fixing this issue!
nerdctl on Windows picks up compose.yaml automatically
The nerdctl command on Windows used to run from a separate directory before and therefore did not locate default filenames like compose.yaml correctly. This has been fixed.
Rancher Desktop is now available as a separate RPM for Fedora
Deprecations
MSI installer no longer installs WSL2 on Windows
WSL2 must be installed on the local system before Rancher Desktop can be installed.
macOS 12 Monterey and earlier are no longer supported
Rancher Desktop no longer works on Apple ARM computers running macOS 12 Monterey. It still works on Apple Intel computers, but is unsupported.
Updates to Bundled Utilities
- amazon-eco-credential-helper 0.9.0 → 0.9.1
- docker 27.4.1 → 27.5.1
- docker-buildx 0.19.3 → 0.20.1
- docker-compose 2.32.1 → 2.33.0
- docker-credential-helpers unchanged 0.8.2
- helm 3.16.4 → 3.17.1
- kuberlr unchanged 0.5.2
- moby/buildkit 0.18.1 → 0.19.0
- nerdctl 2.0.2 → 2.0.3
- spin 3.1.1 → 3.1.2
- spin-shim 0.17.0 → 0.18.0
- spinkube unchanged 0.4.0
- trivy 0.58.1 → 0.59.1
Connect with the developers
- The issue queue
- Rancher Users Slack in the #rancher-desktop channel
Changelog
The full version changelog, from v1.17.0, can be found using GitHub compare and the details of the re

This is the 1.18.0 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Notable Changes and Bug Fixes
Cluster dashboard has been updated from 2.7.0 to 2.11.0
The cluster dashboard has been reimplemented as a Rancher extension and is mostly in sync with the upstream version.
The dashboard now works correctly even when the KUBECONFIG environment variable points to multiple config files.
Network fixes
The gvisor-tap-vsock dependency has been updated again, which has solved several networking regressions from Rancher Desktop 1.17.x (on all platforms).
Rancher Desktop is working properly again when behind a VPN. On macOS the VZ emulation mode works again even without a network connection.
Image scanning now scans local images with containerd
This already worked before for moby.
Image scanning results are displayed much faster once the vulnerability databases have been downloaded (for images with many vulnerabilities).
The Open WebUI extension has been updated
If you already have the extension installed, then you must uninstall it from the "Installed" tab of the "Extensions" page (the "Remove" button on the "Catalog" tab does not work correctly in this release).
After you have uninstalled the current version, you can install the new version as usual from the "Catalog" tab.
docker run issues on Windows have been fixed
docker run on Windows would hang indefinitely when reading from STDIN (#2094) or would produce no output when running without the -i option (#3239). Many thanks to @bcxpro for investigating and fixing this issue!
nerdctl on Windows picks up compose.yaml automatically
The nerdctl command on Windows used to run from a separate directory before and therefore did not locate default filenames like compose.yaml correctly. This has been fixed.
Rancher Desktop is now available as a separate RPM for Fedora
Deprecations
MSI installer no longer installs WSL2 on Windows
WSL2 must be installed on the local system before Rancher Desktop can be installed.
macOS 12 Monterey and earlier are no longer supported
Rancher Desktop no longer works on Apple ARM computers running macOS 12 Monterey. It still works on Apple Intel computers, but is unsupported.
Updates to Bundled Utilities
- amazon-eco-credential-helper 0.9.0 → 0.9.1
- docker 27.4.1 → 27.5.1
- docker-buildx 0.19.3 → 0.20.1
- docker-compose 2.32.1 → 2.33.0
- docker-credential-helpers unchanged 0.8.2
- helm 3.16.4 → 3.17.1
- kuberlr unchanged 0.5.2
- moby/buildkit 0.18.1 → 0.19.0
- nerdctl 2.0.2 → 2.0.3
- spin 3.1.1 → 3.1.2
- spin-shim 0.17.0 → 0.18.0
- spinkube unchanged 0.4.0
- trivy 0.58.1 → 0.59.1
Connect with the developers
- The issue queue
- Rancher Users Slack in the #rancher-desktop channel
Changelog
The full version changelog, from v1.17.0, can be found using GitHub compare and the details of the release can be found in the v1.18.0 milestone.

This is the 1.17.1 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.
Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
What has changed in 1.17.1
Windows installer no longer installs WSL2
Due to Windows Subsystem for Linux installer changes, we no longer attempt to install WSL2 as part of our installer. Please install it separately following the Microsoft instructions before running the Rancher Desktop installer.
For administrative installs, please set the WSLINSTALLED property to 1 as before if suppressing the installer check is desired.
Windows Networking fixes
Downgraded gvisor-tap-vsock to v0.7.5 to resolve DNS failures observed in v0.8.1. This restores DNS resolution behind VPNs and fixes other name resolution issues.
macOS networking changes
It is now possible again to run Rancher Desktop while offline.
DNS changes due to connecting or disconnecting from a VPN are propagated automatically and don't require an app restart.
AppImage works again on Rocky 9 and others
In addition Ubuntu 24.04+ made some changes that make its default configuration incompatible with most AppImages containing Electron-based apps (they crash with a TRAP error). A workaround is to run the AppImage with the --no-sandbox --disable-gpu-sandbox options. Alternatively you can enable unprivileged user namespaces with
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
Updates to Bundled Utilities in 1.17.1
- docker 27.4.1 → 27.5.0
- docker-compose 2.32.1 → 2.32.4
- helm 3.16.4 → 3.17.0
- spin 3.1.1 → 3.1.2
- spin-shim 0.17.0 → 0.18.0
- trivy 0.58.1 → 0.58.2
Changelog
The full version changelog, from v1.17.0, can be found using GitHub compare and the details of the release can be found in the v1.17.1 milestone.
Release notes for 1.17.0
Open WebUI extension
Rancher Desktop now includes the "Open WebUI" extension. If not already present, it will download and install Ollama on the host (to have access to the GPU) and it will also run Open WebUI and SearXNG in containers to make it easy to explore and experiment with different LLM models. Working with LLMs using Open WebUI has more information.
RPM package works again on openSUSE
openSUSE made a change to QEMU that was incompatible with the RPM release of Rancher Desktop; the AppImage bundles its own copy of QEMU and was unaffected. Rancher Desktop 1.17.0 is compatible again with the version of QEMU used by the latest releases of openSUSE.
QEMU and Apple M4
Apple's M4 CPU was not supported by QEMU in earlier releases of Rancher Desktop (VZ was unaffected). 1.17.0 ships with a version of QEMU that has been fixed to work with M4 CPUs.
The 1.15.0 release was supposed to be fully native for Apple Silicon, but it turned out that the applet to prompt for the sudo password was still Intel-only. Now Rosetta should really no longer be needed for Rancher Desktop.
Bundled k3s versions list
Rancher Desktop cannot start unless it has a list of available k3s versions. This has led to problems if the version list could not be determined at first start or after a factory reset. 1.17.0 bundles a k3s version list, which is up-to-date as of the release data of Rancher Desktop. As a result, the app will always have a list of available versions; it will only be potentially missing new versions released after 1.17.0 itself.
Networking improvements
Networking improvements have been made across all platforms, with updates to both upstream libraries and Rancher Desktop itself:
- Enabled UDP Port Forwarding when a network tunnel is active (#6821).
- Added support for the host network driver (--net=host) in both Docker and containerd engines (#7378).
- Resolved Docker Compose network TCP (RST) issues (#7720).
- Restored iptables scanning for Kubernetes ports in CNI-DN-* that were previously overlooked (#7722).
- Addressed performance inefficiencies in the guestAgent process on Windows (#7763), (#7782), (#7825), (#

This is the 1.17.0 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Notable Changes and Bug Fixes
Open WebUI extension
Rancher Desktop now includes the "Open WebUI" extension. If not already present, it will download and install Ollama on the host (to have access to the GPU) and it will also run Open WebUI and SearXNG in containers to make it easy to explore and experiment with different LLM models. Working with LLMs using Open WebUI has more information.RPM package works again on openSUSE
openSUSE made a change to QEMU that was incompatible with the RPM release of Rancher Desktop; the AppImage bundles its own copy of QEMU and was unaffected. Rancher Desktop 1.17.0 is compatible again with the version of QEMU used by the latest releases of openSUSE.QEMU and Apple M4
Apple's M4 CPU was not supported by QEMU in earlier releases of Rancher Desktop (VZ was unaffected). 1.17.0 ships with a version of QEMU that has been fixed to work with M4 CPUs.The 1.15.0 release was supposed to be fully native for Apple Silicon, but it turned out that the applet to prompt for the sudo password was still Intel-only. Now Rosetta should really no longer be needed for Rancher Desktop.Bundled k3s versions list
Rancher Desktop cannot start unless it has a list of available k3s versions. This has led to problems if the version list could not be determined at first start or after a factory reset. 1.17.0 bundles a k3s version list, which is up-to-date as of the release data of Rancher Desktop. As a result, the app will always have a list of available versions; it will only be potentially missing new versions released after 1.17.0 itself.Networking improvements
Networking improvements have been made across all platforms, with updates to both upstream libraries and Rancher Desktop itself:
- Enabled UDP Port Forwarding when a network tunnel is active (#6821).
- Added support for the host network driver (--net=host) in both Docker and containerd engines (#7378).
- Resolved Docker Compose network TCP (RST) issues (#7720).
- Restored iptables scanning for Kubernetes ports in CNI-DN-* that were previously overlooked (#7722).
- Addressed performance inefficiencies in the guestAgent process on Windows (#7763), (#7782), (#7825), (#7891), and (#7558).
Known Issues
MSI installer does not install missing WSL on Windows 11 (#7975)
The Rancher Desktop install does not correctly process the latest output from the wsl --version command on Windows 11 and fails to install WSL2 if it is not already present. The workaround is to manually install WSL2 before installing Rancher Desktop.VZ emulation no longer works offline
Due to a change in a networking dependency, it is no longer possible to run VMs using VZ emulation while offline. QEMU is unaffected. Stay with 1.16.0 if you require VZ mode to work while disconnected.spinkube operator has incompatible changes
The spinkube operator has been updated to version 0.4.0, which had incompatible API changes; it is likely that all applications using it need to be redeployed.Deprecations
macOS 12 Monterey and earlier are no longer supported
Apple usually only provides security updates for the last 3 major macOS releases. GitHub removes CI runners once the OS is no longer supported. Due to availability of hardware resources and software dependencies, we may be unable to create new Rancher Desktop releases compatible with older macOS versions.While Rancher Desktop 1.17.0 seems to work fine on macOS 12 Monterey, it should be considered unsupported.The status of macOS 11 Big Sur is unknown, so auto-upgrade will not offer an upgrade to 1.17.0 on Big Sur or earlier.Updates to Bundled Utilities
- amazon-eco-credential-helper unchanged 0.9.0
- docker 27.2.1 → 27.4.1
- docker-buildx 0.17.1 → 0.19.3
- docker-compose 2.29.5 → 2.32.1
- docker-credential-helpers unchanged 0.8.2
- helm 3.16

This is the 1.15.1 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
What has changed in 1.15.1
- Windows only: Resolved a socket leak when using Kubernetes or other containers from WSL distributions, eventually causing connections to stop working after running out of file descriptors. (#7331)
- macOS and Linux only: Resolved an issue where the inability to manage .bashrc/.zshrc/etc., broke the ability to automatically start Rancher Desktop when the user logs in. (#7337)
Release notes for 1.15.0
Notable Features & Changes
Kubernetes versions before 1.21.0 are no longer supported
If you are on an earlier version, updating to Rancher Desktop 1.15.0 will automatically update you to Kubernetes 1.21.14. If you must continue to use an older version, you should stay on Rancher Desktop 1.14.2.kuberlr and kubectl are native binaries for macOS on Apple Silicon
Rosetta is no longer needed for Rancher Desktop.New networking tunnel stack is now the only option on Windows
It is no longer possible to select the legacy networking mode.On macOS the socket_vmnet has replaced vde_vmnet
It is a complete superset of the old functionality, and the old setting is no longer available.Important Bug Fixes
Shell profile settings are not accidentally deleted
When Rancher Desktop started either after a fresh install, or after a factory reset, and the computer was without internet access, then there was a race condition that could result in the deletion of shell profiles (.bash_profile, .zshrc, etc) (#7154).This race condition has been fixed. However, the code has been updated to always keep a backup file around, just in case there is another undiscovered way to trigger a similar bug.A memory leak on Windows has been fixed that could lead to a frozen system
This issue in the tray menu updater was diagnosed and fixed by @mikeseese (#7238). Thank you for your help!Port forwarding bug with older Kubernetes versions on Windows has been fixed.
For Kubernetes 1.25 versions older than 1.25.3, 1.24 versions older than 1.24.7, or any version before 1.23.13 the port forwarding to the host was not working (#5341). This has been fixed.Known Issues
Container Dashboard
The dashboard does not update automatically when container states have changed or new containers are introduced (#5775).Extensions Install - Allowed Images
When using the Allowed Images feature and also specifying extensions in a deployment profile, the extension images must be included in both lists (#4920).Deprecations
macOS 11 Big Sur and earlier are no longer officially supported
Apple usually only provides security updates for the last 3 major macOS releases. GitHub removes CI runners once the OS is no longer supported. Due to availability of hardware resources and software dependencies, we may be unable to create new Rancher Desktop releases compatible with older macOS versions in the future.We will try not to break Rancher Desktop on older macOS versions as long as reasonably possible, but those versions should be considered unsupported.Updates to Bundled Utilities
- docker 26.1.0 → 27.1.1
- docker-buildx 0.14.1 → 0.16.2
- docker-compose 2.27.1 → 2.29.1
- docker-credential-ecr-login unchanged 0.8.0
- helm 3.15.1 → 3.15.3
- moby/buildkit unchanged 0.12.5
- nerdctl unchanged 1.7.6
- spin: new 2.5.1
- spin-shim: 0.14.1 → 0.15.1
- spinkube: unchanged 0.2.0
- trivy 0.51.4 → 0.53.0
Connect with the developers
- The issue queue
- Rancher Users Slack in the #rancher-desktop channel
Changelog
The full version changelog, from v1.14.2, can be found using GitHub compare and the details of the release can be found in the v1.15.0 milestone.

This is the 1.14.2 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
What has changed in 1.14.2
This release is mostly identical to 1.14.1 with the single exception being the spin executable for macOS. Since it is being notarized, it had to be signed with the hardened runtime, which broke the functionality of running applications natively (not in a container or on Kubernetes) via spin up. In the 1.14.2 release, the macOS spin binaries are signed with the com.apple.security.cs.allow-unsigned-executable-memory entitlement to allow native code generation.We are not enabling auto-update for the 1.14.2 release because the percentage of affected users will be very small. You need to manually update if you are on macOS and want to run spin up.What has changed in 1.14.1
Cluster Explorer would no longer dynamically refresh in 1.14.0 because the web socket connection had been broken. This issue has been fixed (#6968).There are no other changes in 1.14.1.Full Changelog: The full version changelog, from v1.14.0, can be found using GitHub compare.Release Notes for 1.14.0
Notable Features & Changes
Bundles the spin cli (experimental)
Rancher Desktop now includes the spin CLI to support building Wasm images.The js2wasm and kube plugins, as well as the default templates, are installed the first time the WebAssembly support option has been selected in the Container Engine settings.The plugins and templates are also installed into any distro for which WSL Integration has been enabled.Option to install the spinkube operator (experimental)
Rancher Desktop now has an option to install the spinkube operator in the Kubernetes settings to support running Spin applications on Kubernetes. It will install and configure cert-manager and the spin-operator into the cluster. This option requires that WebAssembly support is enabled.The tunnelling network on Windows supports WSL integration
Containers and Kubernetes services can now be accessed from other WSL distributions, as long as WSL Integration is enabled for them.The tunnelling network implementation is now complete and has become the default setting in this release (for new installations or after a factory reset). Support for the legacy network is scheduled to be removed in the following release (1.15.0).The timezone inside the VM now matches the timezone on the host
This means CronJobs in Kubernetes can now be specified using localtime.Known Issues
Windows Networking
There is a known issue with the new network not including all aliased domains (#5239).Container Dashboard
The dashboard does not update automatically when container states have changed or new containers are introduced (#5775).Extensions Install - Allowed Images
When using the Allowed Images feature and also specifying extensions in a deployment profile, the extension images must be included in both lists (#4920).Deprecations
The legacy networking stack on Windows will be removed in 1.15.0
The tunnelling network on Windows has become the default in this release and should be a full superset of the legacy stack capabilities.We are planning to remove the legacy networking mode in 1.15.0.vde_vmnet will be removed in 1.15.0
The socket_vmnet daemon provides all the functionality required by Rancher Desktop and is actively maintained while vde_vmnet itself is deprecated.VZ emulation already uses socket_vmnet unconditionally because it never had support for vde_vmnet.The option will be removed and socket_vmnet will automatically be used when Administrative Access is enabled.Kubernetes versions before 1.21.0 will no longer be supported in 1.15.0
Kubernetes only maintains updates for the latest 3 minor releases (so right now only for 1.27.0 and up). Rancher Desktop tries to support a wider range of legacy versions, but sometimes it becomes necessary to remove support for older versions to 

This is the 1.13.1 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
What has changed in 1.13.1
- Windows only: The minimum WSL kernel requirement (5.15.0.0 or higher) introduced in the v1.13.0 release is no longer required; as a result, the Rancher Desktop installer no longer automatically upgrades WSL. (#6606, #6624)
Full Changelog: The full version changelog, from v1.13.0, can be found using GitHub compare.Release Notes for 1.13.0
Notable Features & Changes
WebAssembly/Wasm support (experimental)
Rancher Desktop can now be configured to run WebAssembly applications in addition to Linux containers. It includes the Spin runtime, and additional wasm shims can be installed manually.WebAssembly is currently supported as a stand-alone container running on the moby engine, or in Kubernetes pods running with containerd.Turning on Wasm support with the moby engine will change the location where images are stored, so all previously downloaded or built images become inaccessible. You may want to run docker system prune --all to reclaim the space (if you don't plan on disabling Wasm support again).Wasm support will be locked and disabled if the machine has a locked profile installed that uses schema version 10 or earlier. You will need to use schema version 11 to unlock.Cluster Dashboard button
Rancher Desktop now displays a "Cluster Dashboard" button in the navigation bar on the left side of the window. This is purely for discovery, as many users have been unaware that this functionality exists; the button performs the same action as the "Cluster Dashboard" menu item in the notification icon context menu.The button is only displayed when Kubernetes is enabled.Important Bug Fixes
~/.kube/config in WSL distros (Windows)
Rancher Desktop up to version 1.11 used a symlink from ~/.kube/config inside WSL distributions back to the Windows version of this config file (when WSL integration is enabled).In Rancher Desktop 1.12, this symlink had to be replaced by a separate config file inside WSL because Kubernetes would use a different IP address when using the tunneling network stack (it runs inside a separate network namespace). This meant that the user had to maintain multiple config files and the kube context inside a distro could be different from the Windows side.In this 1.13 release, we are running a tunnel to the WSL network namespace; this means Kubernetes is again reachable via 127.0.0.1 from both Windows and the WSL distros. The separate ~/.kube/config files inside the distros will be converted back into a symlink, but only if it contains no other information than the Rancher Desktop cluster itself. If there is additional configuration data, then the user will have to perform the data merging manually if they want to get back to using a symlink as well.Support for QEMU on M3 machines (macOS)
QEMU for Apple Silicon machines has been updated to version 8.2.1 and now supports the M3 CPU architecture as well.Support for kind (macOS and Linux only)
This release supports kind on macOS and Linux as long as Kubernetes is either disabled or running Kubernetes 1.20.4 or higher (older Kubernetes versions require cgroups v1, which is incompatible with kind).Experimental virtiofs mount type could delete $HOME directory data (Linux only)
This serious bug has been fixed.Note that on Linux this setting requires the Rust implementation of virtiofsd to be installed on the host; otherwise it won't work.Experimental 9p mount type now works correctly for RPM and DEB installation (Linux only)
It is still not working in the AppImage install.Known Issues
Windows Networking
There is a known issue with the new network not including all aliased domains (#5239).Container Dashboard
The dashboard does not update automatically when container states have changed or new containers are introduced (#5775).Extens

This is the 1.13 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.Updated Windows Requirements
This release requires a newer WSL kernel release (5.15.0.0 or higher) than previous releases. You can check the currently installed version with this command:

C:\>wsl uname -r
5.15.133.1-microsoft-standard-WSL2

If necessary, the installer will attempt to upgrade WSL via the Microsoft Store, but if that fails because the user doesn't have permissions, then the installation or upgrade of Rancher Desktop will fail so the user will have to upgrade WSL on their own.Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Notable Features & Changes
WebAssembly/Wasm support (experimental)
Rancher Desktop can now be configured to run WebAssembly applications in addition to Linux containers. It includes the Spin runtime, and additional wasm shims can be installed manually.WebAssembly is currently supported as a stand-alone container running on the moby engine, or in Kubernetes pods running with containerd.Turning on Wasm support with the moby engine will change the location where images are stored, so all previously downloaded or built images become inaccessible. You may want to run docker system prune --all to reclaim the space (if you don't plan on disabling Wasm support again).Wasm support will be locked and disabled if the machine has a locked profile installed that uses schema version 10 or earlier. You will need to use schema version 11 to unlock.Cluster Dashboard button
Rancher Desktop now displays a "Cluster Dashboard" button in the navigation bar on the left side of the window. This is purely for discovery, as many users have been unaware that this functionality exists; the button performs the same action as the "Cluster Dashboard" menu item in the notification icon context menu.The button is only displayed when Kubernetes is enabled.Important Bug Fixes
~/.kube/config in WSL distros (Windows)
Rancher Desktop up to version 1.11 used a symlink from ~/.kube/config inside WSL distributions back to the Windows version of this config file (when WSL integration is enabled).In Rancher Desktop 1.12, this symlink had to be replaced by a separate config file inside WSL because Kubernetes would use a different IP address when using the tunneling network stack (it runs inside a separate network namespace). This meant that the user had to maintain multiple config files and the kube context inside a distro could be different from the Windows side.In this 1.13 release, we are running a tunnel to the WSL network namespace; this means Kubernetes is again reachable via 127.0.0.1 from both Windows and the WSL distros. The separate ~/.kube/config files inside the distros will be converted back into a symlink, but only if it contains no other information than the Rancher Desktop cluster itself. If there is additional configuration data, then the user will have to perform the data merging manually if they want to get back to using a symlink as well.Support for QEMU on M3 machines (macOS)
QEMU for Apple Silicon machines has been updated to version 8.2.1 and now supports the M3 CPU architecture as well.Support for kind (macOS and Linux only)
This release supports kind on macOS and Linux as long as Kubernetes is either disabled or running Kubernetes 1.20.4 or higher (older Kubernetes versions require cgroups v1, which is incompatible with kind).Experimental virtiofs mount type could delete $HOME directory data (Linux only)
This serious bug has been fixed.Note that on Linux this setting requires the Rust implementation of virtiofsd to be installed on the host; otherwise it won't work.Experimental 9p mount type now works correctly for RPM and DEB installation (Linux only)
It is still not working in the AppImage install.Known Issues
Windows Networking
There is a known issue with the new network not including all aliased domains (#5239).Container Dashboard
T

This is the 1.12.3 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to Mac, Windows, and Linux.⚠️ Warning ⚠️
Do NOT use the experimental virtiofs mount type (on Linux and macOS). We have experienced catastrophic data loss with this mount option on Linux (the $HOME directory on the host was wiped out), and have seen a single bug report on Lima claiming a similar experience on macOS. We are not aware of a direct incidence with Rancher Desktop on macOS, but Lima is the underlying technology managing the VM and volume mounts.Due to the catastrophic failure mode we urge everyone to NOT use this option.We will temporarily remove this setting in the 1.13.0 release until the issue is understood and fixed.Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
What has changed in 1.12.3
The 1.12.3 patch release updates runc to version 1.1.12, buildkitd to 0.12.5, and nerdctl to 1.7.3 to fix a number of CVEs:- CVE-2024-21626 Several container breakouts due to internally leaked fds (high)
- CVE-2024-23650 Possible panic when incorrect parameters sent from frontend (moderate)
- CVE-2024-23651 Possible race condition with accessing subpaths from cache mounts (high)
- CVE-2024-23652 Possible host system access from mount stub cleaner (high)
- CVE-2024-23653 Interactive containers API does not validate entitlements check (high)
All these CVEs can only be exploited if the user is using malicious input in the container build process or is running container images that have already been compromised.The following CVE is not fixed in this patch release because there is no upstream release for moby 23.* that includes the fix yet:- CVE-2024-24557 Classic builder cache poisoning (moderate)
Note that Rancher Desktop is only affected by this CVE if the user explicitly opts out of Buildkit to use the legacy/classic builder (sets DOCKER_BUILDKIT=0). It does not apply to the default configuration.What has changed in 1.12.2
The 1.12.2 patch release fixes a single issue on macOS and Linux where the shell profile (e.g. ~/.bash_profile) could be deleted (#6281). This was due to a race condition, after either a fresh install or a factory-reset, which would display the first-run dialog. When this dialog was closed (accepted) quickly, the file could be overwritten with truncated content.There are no changes (except for the version number bump) on Windows.What has changed in 1.12.1
The 1.12.1 patch release fixes a single memory corruption issue on Windows for importing CA certificates (#6308). There are no changes (except for the version number bump) on macOS and Linux.Release notes for 1.12.0
Notable Features & Changes
Windows WSL Installation
For Windows users that have previously overridden the WSL installation check, please use WSLINSTALLED instead of WSLKERNELINSTALLED.Windows tunnelling networking mode is no longer experimental
It has feature parity with the legacy networking mode and will become the default setting for new installations (and factory reset) in the 1.13 release. We expect to remove the legacy networking support in 1.14.macOS builds for aarch64 are now native binaries
The VM code has always been platform-native, but the UI used to require Rosetta because it was still an x86_64 binary. Now everything except for kuberlr and the kubectl versions managed by it are aarch64 binaries. The problem with kuberlr and kubectl is that there are no native binaries available from upstream for older Kubernetes versions.macOS socket_vmnet networking is no longer experimental
socket_vmnet is a replacement for vde_vmnet, which is deprecated upstream. It was never supported in VZ emulation mode, so Rancher Desktop already uses socket_vmnet in VZ mode when admin access is enabled.socket_vmnet will become the default for QEMU as well in the 1.13 release; in 1.14, vde_vmnet will be removed.Deployment Profiles
This release now requires deployment profiles to have an explicit version field 

Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Connect with the developers
- The issue queue
- Rancher Users Slack in the #rancher-desktop channel

Windows and macOS Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
BuildX Error
- Fixes #5363 where newly created BuildX instances were failing with "cgroup" errors.
WSL Updates
- Fixes #4560 during startup for Rancher Desktop where the WSL integration was executing distributions not explicitly marked for integration and causing startup issues.
- Fixes #5805 where WSL integrations could not be disabled from the UI.
- Fixes #5551 where the WSL version was unable to be properly parsed causing application errors.
Locked No-Proxy Field UI Update
- Fixes #5468 where the No proxy hostname list was editable in the UI after being locked via deployment policy.
VZ Emulation
- Fixes #5542 where an incompatible mount type could be set for VZ emulation using the command line and rdctl.
Deployment Profile - Windows
- Fixes #5857 where deployment profiles created via rdctl with locked fields were not able to initialize the application.
Updates to Bundled Utilities
- helm 3.12.3 → 3.13.1
- docker 24.0.5 → 24.0.6
- docker-buildx 0.11.2 → 0.12.0
- docker-compose 2.20.3 → 2.22.0
- docker-credential-ecr-login 0.7.1 → 0.7.1
- nerdctl 1.5.0 → 1.6.2
- moby/buildkit 0.11.6 → 0.12.3
- trivy 0.44.1 → 0.46.0
Connect With the Developers
- The issue queue
- Rancher Users Slack in the #rancher-desktop channel

Windows and macOS Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
Deployment Profile Updates
- Rancher Desktop now supports generating Windows .reg or macOS .plist files using the rdctl create-profile [options] command.
Please see the command reference for documentation.
Mount Type virtiofs Available on Linux & macOS
- Initially available for macOS, this release adds the virtiofs mount type for Linux environments as well.
This can be set as an option on the Virtual Machine | Volumes tab.
Windows Proxy Update
- The WSL noproxy list is now displayed in a text area from the preferences dialog via Preferences > WSL > Proxy.
Desktop Extensions - Switching Container Engines
- Fixes #4788 where Rancher Desktop will now silently remove incompatible extensions when switching container engines between the dockerd and containerd options.
Deployment Profile Updates
- Fixes #4952 where an incorrect Kubernetes version value in a deployment profile was not terminating the application.
- Fixes #5047 with editable Kubernetes fields in locked deployment profiles.
Windows Network Update
- Fixes #5396 where port binding to localhost failed when using a moby backend engine and allows for exposed ports to be discoverable in the namespaced network.
Windows Proxy Update
- Fixes #5366 where users were unable to delete a host from the No proxy hostname list.
Allowed Images List & rdctl create-profile --output=reg
- There is a known issue #5466 where an empty allowed images list is not being output while using the command rdctl create-profile --output=reg --from-settings.
Updates to Bundled Utilities
- helm 3.12.0 → 3.12.3
- docker 24.0.2 → 24.0.5
- docker-buildx 0.10.5 → 0.11.2
- docker-compose 2.18.0 → 2.20.3
- docker-credential-ecr-login 0.7.1 → 0.7.1
- nerdctl 1.4.0 → 1.5.0
- moby/buildkit 0.12.0 → 0.11.6 (downgrade due to an issue with cgroups)
- trivy 0.42.0 → 0.44.1
Connect With the Developers
- The issue queue
- Rancher Users Slack in the #rancher-desktop channel

Windows and macOS Installers
- Windows
- macOS x86_64
- macOS aarch64
- Linux install notes
New networking stack on Windows
- The new networking code would break when the user name contained a space.
- Port forwarding did not work with the new networking code.
Updates to bundled utilities
- helm 3.12.0 → 3.12.1
- docker-buildx 0.10.5 → 0.11.0
- docker-compose 2.18.1 → 2.19.0
- trivy 0.42.0 → 0.42.1
Connect with the developers
- The issue queue
- Rancher Users Slack in the #rancher-desktop channel