This is the 1.15.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 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 keep the code maintainable while adding new features.

We intend to remove support for Kubernetes versions before 1.21.0 in Rancher Desktop 1.15.0.

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 25.0.4 → 26.1.0
• docker-buildx 0.13.0 → 0.14.1
• docker-compose 2.24.7 → 2.27.1
• docker-credential-ecr-login 0.7.1 → 0.8.0
• helm 3.14.2 → 3.15.1
• moby/buildkit unchanged 0.12.5
• nerdctl 1.7.3 → 1.7.6
• spin: new 2.5.1
• spin-shim: 0.11.1 → 0.14.1
• spinkube: new 0.2.0
• trivy 0.49.1 → 0.51.4

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.13.1, can be found using GitHub compare and the details of the release can be found in the v1.14.0 milestone.

This is the 1.14.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.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 keep the code maintainable while adding new features.

We intend to remove support for Kubernetes versions before 1.21.0 in Rancher Desktop 1.15.0.

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 25.0.4 → 26.1.0
• docker-buildx 0.13.0 → 0.14.1
• docker-compose 2.24.7 → 2.27.1
• docker-credential-ecr-login 0.7.1 → 0.8.0
• helm 3.14.2 → 3.15.1
• moby/buildkit unchanged 0.12.5
• nerdctl 1.7.3 → 1.7.6
• spin: new 2.5.1
• spin-shim: 0.11.1 → 0.14.1
• spinkube: new 0.2.0
• trivy 0.49.1 → 0.51.4

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.13.1, can be found using GitHub compare and the details of the release can be found in the v1.14.0 milestone.

This is the 1.14 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 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 keep the code maintainable while adding new features.

We intend to remove support for Kubernetes versions before 1.21.0 in Rancher Desktop 1.15.0.

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 25.0.4 → 26.1.0
• docker-buildx 0.13.0 → 0.14.1
• docker-compose 2.24.7 → 2.27.1
• docker-credential-ecr-login 0.7.1 → 0.8.0
• helm 3.14.2 → 3.15.1
• moby/buildkit unchanged 0.12.5
• nerdctl 1.7.3 → 1.7.6
• spin: new 2.5.1
• spin-shim: 0.11.1 → 0.14.1
• spinkube: new 0.2.0
• trivy 0.49.1 → 0.51.4

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.13.1, can be found using GitHub compare and the details of the release can be found in the v1.14.0 milestone.

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).

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).

Updates to Bundled Utilities

• docker 24.0.7 → 25.0.4
• docker-buildx 0.12.0 → 0.13.0
• docker-compose 2.23.3 → 2.24.7
• docker-credential-ecr-login 0.8.0 → 0.8.1
• helm 3.13.3 → 3.14.2
• moby/buildkit 0.12.3 → 0.12.5
• nerdctl 1.7.1 → 1.7.3
• trivy 0.48.0 → 0.49.1

Bundled Wasm shims

The spin shim comes from the containerd-wasm-shims release 0.11.1.

• Spin version 2.2.0

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.12.3, can be found using GitHub compare and the details of the release can be found in the v1.13.0 milestone.

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

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).

Updates to Bundled Utilities

• docker 24.0.7 → 25.0.4
• docker-buildx 0.12.0 → 0.13.0
• docker-compose 2.23.3 → 2.24.7
• docker-credential-ecr-login 0.8.0 → 0.8.1
• helm 3.13.3 → 3.14.2
• moby/buildkit 0.12.3 → 0.12.5
• nerdctl 1.7.1 → 1.7.3
• trivy 0.48.0 → 0.49.1

Bundled Wasm shims

The spin shim comes from the containerd-wasm-shims release 0.11.1.

• Spin version 2.2.0

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.12.3, can be found using GitHub compare and the details of the release can be found in the v1.13.0 milestone.

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.

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 (which is 10, as of release 1.11.0).

The version of rdctl that ships with this release will have the version field in any generated deployment files. However, this means that existing files will either need to be regenerated or manually edited in place.

• For Linux, add "version": 10, at the very start of the JSON-formatted deployment file immediately after
  the initial open brace {.

• For macOS, add <key>Version</key><integer>10</integer> after the initial <dict> tag.

• For Windows, add a DWORD value named version with value 10 (hexadecimal a) at the top level of each profile that needs updating.

Important Bug Fixes

Snapshots

Improvements and fixes regarding executing multiple application actions while a snapshot is undergoing a management activity (#5846, #5848, #5849, and #5854).

Known Issues

Apple M3 CPUs

Apple M3 CPUs are not supported (yet) by QEMU. Please use VZ emulation instead (#5943).

Snapshots

There is a known issue with the Snapshot Cancel operation in the UI. It is possible that the operation can no longer be cancelled when the button is pressed. In that case, the operation may succeed but the UI will still claim that it has been cancelled (#6159).

Windows Networking

There is a known issue with the new network not including all aliased domains (#5239).

Container Dashboard

There are known issues with the Container Dashboard when using the nerdctl container engine; one is that the "Started" field shows an inaccurate time for containers starting up. The dashboard also has an issue updating when container states have changed or new containers are introduced (#6191, #6189, #5877, and #5775).

Provisioning Scripts - Windows

The location for provisioning scripts on Windows has changed from %AppData%\rancher-desktop\provisioning to %LocalAppData%\rancher-desktop\provisioning. The files are not automatically migrated when Rancher Desktop is updated, so they must be manually moved or copied to the new location.

9p - Linux OS

There is a known issue with some Linux distributions and using the experimental mount type 9p (#4943).

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).

Updates to Bundled Utilities

• helm 3.12.3 → 3.13.3
• docker 24.0.6 → 24.0.7
• docker-buildx 0.11.2 → 0.12.0
• docker-compose 2.22.0 → 2.23.3
• docker-credential-ecr-login 0.7.1 → 0.7.1
• nerdctl 1.6.2 → 1.7.1
• moby/buildkit 0.12.3 → 0.12.4
• trivy 0.46.0 → 0.46.0

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.12.0, can be found using GitHub compare and the details of the release can be found in the v1.12.0 milestone.

This is the 1.12.2 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to Mac, Windows, and Linux.

Installers

• Windows
• macOS x86_64
• macOS aarch64
• Linux install notes

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

Below are the release notes for 1.20.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 (which is 10, as of release 1.11.0).

The version of rdctl that ships with this release will have the version field in any generated deployment files. However, this means that existing files will either need to be regenerated or manually edited in place.

• For Linux, add "version": 10, at the very start of the JSON-formatted deployment file immediately after
  the initial open brace {.

• For macOS, add <key>Version</key><integer>10</integer> after the initial <dict> tag.

• For Windows, add a DWORD value named version with value 10 (hexadecimal a) at the top level of each profile that needs updating.

Important Bug Fixes

Snapshots

Improvements and fixes regarding executing multiple application actions while a snapshot is undergoing a management activity (#5846, #5848, #5849, and #5854).

Known Issues

Apple M3 CPUs

Apple M3 CPUs are not supported (yet) by QEMU. Please use VZ emulation instead (#5943).

Snapshots

There is a known issue with the Snapshot Cancel operation in the UI. It is possible that the operation can no longer be cancelled when the button is pressed. In that case, the operation may succeed but the UI will still claim that it has been cancelled (#6159).

Windows Networking

There is a known issue with the new network not including all aliased domains (#5239).

Container Dashboard

There are known issues with the Container Dashboard when using the nerdctl container engine; one is that the "Started" field shows an inaccurate time for containers starting up. The dashboard also has an issue updating when container states have changed or new containers are introduced (#6191, #6189, #5877, and #5775).

Provisioning Scripts - Windows

The location for provisioning scripts on Windows has changed from %AppData%\rancher-desktop\provisioning to %LocalAppData%\rancher-desktop\provisioning. The files are not automatically migrated when Rancher Desktop is updated, so they must be manually moved or copied to the new location.

9p - Linux OS

There is a known issue with some Linux distributions and using the experimental mount type 9p (#4943).

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).

Updates to Bundled Utilities

• helm 3.12.3 → 3.13.3
• docker 24.0.6 → 24.0.7
• docker-buildx 0.11.2 → 0.12.0
• docker-compose 2.22.0 → 2.23.3
• docker-credential-ecr-login 0.7.1 → 0.7.1
• nerdctl 1.6.2 → 1.7.1
• moby/buildkit 0.12.3 → 0.12.4
• trivy 0.46.0 → 0.46.0

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.12.0, can be found using GitHub compare and the details of the release can be found in the v1.12.0 milestone.

This is the 1.12.1 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to Mac, Windows, and Linux.

Installers

• Windows
• macOS x86_64
• macOS aarch64
• Linux install notes

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

Below are the release notes for 1.20.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 (which is 10, as of release 1.11.0).

The version of rdctl that ships with this release will have the version field in any generated deployment files. However, this means that existing files will either need to be regenerated or manually edited in place.

• For Linux, add "version": 10, at the very start of the JSON-formatted deployment file immediately after
  the initial open brace {.

• For macOS, add <key>Version</key><integer>10</integer> after the initial <dict> tag.

• For Windows, add a DWORD value named version with value 10 (hexadecimal a) at the top level of each profile that needs updating.

Important Bug Fixes

Snapshots

Improvements and fixes regarding executing multiple application actions while a snapshot is undergoing a management activity (#5846, #5848, #5849, and #5854).

Known Issues

Apple M3 CPUs

Apple M3 CPUs are not supported (yet) by QEMU. Please use VZ emulation instead (#5943).

Snapshots

There is a known issue with the Snapshot Cancel operation in the UI. It is possible that the operation can no longer be cancelled when the button is pressed. In that case, the operation may succeed but the UI will still claim that it has been cancelled (#6159).

Windows Networking

There is a known issue with the new network not including all aliased domains (#5239).

Container Dashboard

There are known issues with the Container Dashboard when using the nerdctl container engine; one is that the "Started" field shows an inaccurate time for containers starting up. The dashboard also has an issue updating when container states have changed or new containers are introduced (#6191, #6189, #5877, and #5775).

Provisioning Scripts - Windows

The location for provisioning scripts on Windows has changed from %AppData%\rancher-desktop\provisioning to %LocalAppData%\rancher-desktop\provisioning. The files are not automatically migrated when Rancher Desktop is updated, so they must be manually moved or copied to the new location.

9p - Linux OS

There is a known issue with some Linux distributions and using the experimental mount type 9p (#4943).

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).

Updates to Bundled Utilities

• helm 3.12.3 → 3.13.3
• docker 24.0.6 → 24.0.7
• docker-buildx 0.11.2 → 0.12.0
• docker-compose 2.22.0 → 2.23.3
• docker-credential-ecr-login 0.7.1 → 0.7.1
• nerdctl 1.6.2 → 1.7.1
• moby/buildkit 0.12.3 → 0.12.4
• trivy 0.46.0 → 0.46.0

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.12.0, can be found using GitHub compare and the details of the release can be found in the v1.12.0 milestone.

This is the 1.12 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to Mac, Windows, and Linux.

Installers

• Windows
• macOS x86_64
• macOS aarch64
• Linux install notes

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 (which is 10, as of release 1.11.0).

The version of rdctl that ships with this release will have the version field in any generated deployment files. However, this means that existing files will either need to be regenerated or manually edited in place.

• For Linux, add "version": 10, at the very start of the JSON-formatted deployment file immediately after
  the initial open brace {.

• For macOS, add <key>Version</key><integer>10</integer> after the initial <dict> tag.

• For Windows, add a DWORD value named version with value 10 (hexadecimal a) at the top level of each profile that needs updating.

Important Bug Fixes

Snapshots

Improvements and fixes regarding executing multiple application actions while a snapshot is undergoing a management activity (#5846, #5848, #5849, and #5854).

Known Issues

Apple M3 CPUs

Apple M3 CPUs are not supported (yet) by QEMU. Please use VZ emulation instead (#5943).

Snapshots

There is a known issue with the Snapshot Cancel operation in the UI. It is possible that the operation can no longer be cancelled when the button is pressed. In that case, the operation may succeed but the UI will still claim that it has been cancelled (#6159).

Windows Networking

There is a known issue with the new network not including all aliased domains (#5239).

Container Dashboard

There are known issues with the Container Dashboard when using the nerdctl container engine; one is that the "Started" field shows an inaccurate time for containers starting up. The dashboard also has an issue updating when container states have changed or new containers are introduced (#6191, #6189, #5877, and #5775).

Provisioning Scripts - Windows

The location for provisioning scripts on Windows has changed from %AppData%\rancher-desktop\provisioning to %LocalAppData%\rancher-desktop\provisioning. The files are not automatically migrated when Rancher Desktop is updated, so they must be manually moved or copied to the new location.

9p - Linux OS

There is a known issue with some Linux distributions and using the experimental mount type 9p (#4943).

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).

Updates to Bundled Utilities

• helm 3.12.3 → 3.13.3
• docker 24.0.6 → 24.0.7
• docker-buildx 0.11.2 → 0.12.0
• docker-compose 2.22.0 → 2.23.3
• docker-credential-ecr-login 0.7.1 → 0.7.1
• nerdctl 1.6.2 → 1.7.1
• moby/buildkit 0.12.3 → 0.12.4
• trivy 0.46.0 → 0.46.0

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.12.0, can be found using GitHub compare and the details of the release can be found in the v1.12.0 milestone.

This is the 1.11.1 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to Mac, Windows, and Linux.

Installers

• Windows
• macOS x86_64
• macOS aarch64
• Linux install notes

The Linux packages and AppImage are not yet available due to technical issues. They will be released within the next 2 days. Note that there are no changes between 1.11.0 and 1.11.1 for the Linux binaries, so there isn't any reason to install the patch release on Linux.

This patch release fixes two issues in Rancher Desktop 1.11.0

Windows

This patch fixes potential corruption of the Windows kube config file in the case whereby a WSL distro uses a symlink to the host file and WSL integration is enabled for this distro. Note that these symlinks may have been created by earlier releases of Rancher Desktop (#5981, #5946).

Rancher Desktop 1.11.1 will replace such symlinks with a separate file. This is necessary because the Kubernetes endpoint is now different between the Windows host and inside a WSL2 distro.

macOS

On macOS in Rancher Desktop 1.11.0, the VM would no longer get a routable IP address even when running with "Administrative Access" (related to vde_vmnet and socket_vmnet drivers). This issue has been fixed (#6051).

Linux

There are no changes related to Linux in this release compared to 1.11.0.

Known Issues

Apple M3 CPUs

There have been multiple reports that QEMU does not work with the latest Apple Silicon. Please use VZ emulation instead (#5943).

Snapshots

Currently there are known issues regarding executing multiple application actions while a snapshot is undergoing a management activity (#5846, #5848, #5849, and #5854). Please don't perform snapshot operations through the GUI and the CLI at the same time.

Container Dashboard

There are known issues with the Container Dashboard with filtering table items, ports being displayed correctly, and if using the nerdctl container engine, there is an issue with the "Started" field showing an inaccurate time for containers starting up. The dashboard also has an issue updating when container states have changed or new containers are introduced (#5759, #5893, #5877, and #5775).

Provisioning Scripts - Windows

The location for provisioning scripts on Windows has changed from %AppData%\rancher-desktop\provisioning to %LocalAppData%\rancher-desktop\provisioning. The files are not automatically migrated when Rancher Desktop is updated, so they must be manually moved or copied to the new location.

9p - Linux OS

There is a known issue with some Linux distributions and using the experimental mount type 9p (#4943).

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).

Please check the Rancher Desktop 1.11.0 release notes for a comprehensive list of new features and bug fixes.

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.11.0, can be found using GitHub compare and the details of the release can be found in the v1.11.0 milestone.

This is the 1.11.0 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.

Windows and macOS Installers

• Windows
• macOS x86_64
• macOS aarch64
• Linux install notes

Notable Features & Changes

Snapshots (Experimental)

Rancher Desktop now has the ability to take snapshots which store the current configuration of your virtual machine and all associated settings. Snapshots can be managed both from the application GUI under the Snapshots tab or on the command line using rdctl snapshot.

Management activities include creating, deleting, and restoring of saved snapshots. Please note that management activities should complete before performing other actions in the application. Concurrent actions are not supported at the moment. Please see the documentation and reference page for more information and known issues below for current limitations

Container Dashboard (Experimental)

The new Containers tab offers quick access to view and manage containers from the application GUI. You can perform control activities such as stop, start, and delete as well as bulk selection/actions on containers that have a similar state. Please view the documentation for more information and known issues below for current limitations.

macOS Networking

You can now use the network configuration socket-vmnet with VZ emulation applied and administrative access enabled.

Windows Networking Tunnel (Experimental)

With the WSL networking tunnel enabled, the WSL integrations have received an update to allow distributions access to the Kubernetes API server hosted in Rancher Desktop's namespace network.

Important Bug Fixes

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.

Known Issues

Snapshots

Currently there are known issues regarding executing multiple application actions while a snapshot is undergoing a management activity (#5846, #5848, #5849, and #5854).

Container Dashboard

There are known issues with the Container Dashboard with filtering table items, ports being displayed correctly, and if using the nerdctl container engine there is an issue with the "Started" field showing an inaccurate time for containers starting up. The dashboard also has an issue updating when container states have changed or new containers are introduced (#5759, #5893, #5877, and #5775).

9p - Linux OS

There is a known issue with some Linux distributions and using the experimental mount type 9p (#4943).

Extensions Install - Allowed Images

When using the Allowed Images feature, and also specifying extensions in a deployment profile, then the extension images must be included in both lists (#4920).

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

Changelog

The full version changelog, from v1.10.0, can be found using GitHub compare and the details of the release can be found in the v1.11.0 milestone.

This is the 1.10.0 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.

Windows and macOS Installers

• Windows
• macOS x86_64
• macOS aarch64
• Linux install notes

New Features

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.

Important Bug Fixes

Desktop Extensions - Switching Container Engines

• Fixes https://github.com/rancher-sandbox/rancher-desktop/issues/4788 where Rancher Desktop will now silently remove incompatible extensions when switching container engines between the dockerd and containerd options.

Deployment Profile Updates

• Fixes https://github.com/rancher-sandbox/rancher-desktop/issues/4952 where an incorrect Kubernetes version value in a deployment profile was not terminating the application.

• Fixes https://github.com/rancher-sandbox/rancher-desktop/issues/5047 with editable Kubernetes fields in locked deployment profiles.

Windows Network Update

• Fixes https://github.com/rancher-sandbox/rancher-desktop/issues/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 https://github.com/rancher-sandbox/rancher-desktop/issues/5366 where users were unable to delete a host from the No proxy hostname list.

Known Issues

Allowed Images List & rdctl create-profile --output=reg

• There is a known issue https://github.com/rancher-sandbox/rancher-desktop/issues/5466 where an empty allowed images list is not being output while using the command rdctl create-profile --output=reg --from-settings.
  A workaround is to add at least one image to the allowed images list, which can point to a non-existing image or registry.

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

Changelog

The full version changelog, from v1.9.1, can be found using GitHub compare and the details of the release can be found in the v1.10.0 milestone.

This is the 1.9.1 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.

Windows and macOS Installers

• Windows
• macOS x86_64
• macOS aarch64
• Linux install notes

Important bug fixes in this patch release

Locked settings could be unlocked

When the main application window was closed and re-opened without terminating the application, then all settings locked by a deployment profile could be edited again. They were only reset to their locked values when Rancher Desktop was restarted.

Uncaught proxy handling errors

The module handling https proxies inside Rancher Desktop was updated to its latest version, which contained a bug tied to handling proxy error messages that contained additional error information in addition to the HTTP status code. This bug would throw an exception that Rancher Desktop would not handle. The module has been downgraded to the previous version again until the bug is fixed upstream.

Other fixes

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.

Buildkit support on Windows

The Rancher Desktop WSL distro did not include the necessary tools to use buildkit on Windows.

Apple Virtualization Framework could not be enabled on macOS 13.0 (Intel) and 13.3 (M1)

This was due to an incorrect version comparison and has been fixed.

Rancher Desktop failed silently when ~/.docker/config.json was invalid

It now displays an error message during startup.

Known issue

The Kubernetes version can be modified via rdctl start --kubernetes.version 1.XX.Y even when it is otherwise locked down by a deployment profile. This is the only setting affected by this bug; Kubernetes versions are updated later once the list of available versions is known.

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

Changelog

The full version changelog, from v1.9.0, can be found using GitHub compare and the details of the release can be found in the v1.9.1 milestones.

This is the 1.9.0 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.

Windows and macOS Installers

• Windows
• macOS x86_64
• macOS aarch64
• Linux install notes

New features

Docker Extensions

This release provides support for Docker Extensions. They can be installed via the UI from a catalog, or via the CLI from any registry.

The extensions in the bundled catalog have been tested to work with Rancher Desktop 1.9. Some extensions only work with the moby container engine; they will not be displayed in the catalog when using containerd.

The Epinio extension only works when Kubernetes has been enabled.

Additional extensions can be installed via the CLI but may not work with Rancher Desktop.

Preferences for experimental settings

The following settings were previously only configurable via rdctl. They have been added to the Preferences dialog, which has been extended with additional tabs:

Windows

• A new networking stack implementation can be selected that works better in VPN environments. This new stack now automatically configures port forwarding as well.

macOS

• Virtual machine type can be set to qemu or vz (Apple Virtualization Framework). vz requires macOS 13.0 Ventura on Intel and macOS 13.3 on Arm (M1, M2) machines. Rosetta can be enabled to run Intel container images on M1/M2 computers under vz emulation.

• Directory mounting can use virtiofs instead of the default reverse-sshfs mode when using vz.

• The socket-vmnet driver can be selected instead of the default vde-vmnet driver. It is only being used when running with administrative privileges to provide a routable (bridged) IP address on the local network.

macOS and Linux

• Directory mounting can use 9p instead of reverse-sshfs. Various parameters of the 9p protocol can be configured as well.

Windows Proxy support

• Many thanks to @tperale for contributing an implementation of proxy support on Windows. The proxy settings can be configured via the Preferences dialog and via rdctl.

Locked Settings in Deployment Profiles

• For enterprise deployments, an administrator can now lock any setting globally to enforce company policy. Locked settings get a 🔒 icon in the Preferences dialog and cannot be modified.

Important bug fixes

Apple Virtualization Framework

• Several fixes to support for VZ emulation mode have been applied.

• Rosetta is now configured correctly.

• The 3 minute timeout during VM shutdown has been fixed.

Kubernetes service port forwarding

Fixes an issue that was introduced in 1.8 in Rancher Desktop Agent where if Kubernetes sends updates for services and the port mappings had not changed, the existing maps are deleted.

Other changes

• The default window size of the application has been increased.

• The default container engine has been changed from containerd to moby. This only affects new installations, and factory-reset.

• By default, Rancher Desktop will no longer request administrative access. That is need for a routable (bridged) IP address, and for creating the Docker socket in the default /var/run/docker.sock location.

  Rancher Desktop also sets up a rancher-desktop docker context and selects it, so having the socket in the default location is not necessary in most situation. Administrative access can be requested via the Preferences dialog.

  This change also only affects new installations, and factory reset. Existing configurations will not be modified.

Updates to bundled utilities

• helm 3.11.2 → 3.12.0
• docker 23.0.1 → 24.0.2
• docker-buildx 0.10.4 → 0.10.5
• docker-compose 2.16.0 → 2.18.1
• docker-credential-ecr-login 0.6.0 → 0.7.1
• nerdctl 1.2.1 → 1.4.0
• trivy 0.38.2 → 0.42.0

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.8.1, can be found using GitHub compare and the details of the release can be found in the v1.9.0-tech-preview and v1.9.0 milestones.

This is the 1.9.0-tech-preview release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to macOS, Windows, and Linux.

New feature

This release provides a preview of the upcoming support for Docker Desktop Extensions. They can be installed via the UI from a catalog, or via the CLI from any registry.

Implementation of extension support is on-going, and this tech preview comes with a catalog of 3 extensions that are known to work with the support already in place:

• Epinio
• Logs-Explorer
• Tachometer

Additional extensions can be installed via rdctl extension install ..., but may possibly not work (yet).

Please use the moby container engine to try out the extensions; "Logs Explorer" and "Tachometer" currently do not work with containerd.

The Epinio extension only works when Kubernetes has been enabled.

Windows and macOS Installers

• Windows
• macOS x86_64
• macOS aarch64

Linux Installation

Because this is not a full release, it cannot be installed as described in the official Rancher Desktop documentation. Instead, follow the developer documentation (scroll past the explanation of version format). This will let you install a development version of Rancher Desktop that has the features associated with the technical preview.

Since the technical preview changes are in the release-1.9 branch, you need to install a version of Rancher Desktop that has release1.9 in it. For example, if installing via rpm, you would use a version that looks like 0.release1.9.1681519864.1234567-7.1.

Important bug fix

Fixes an issue that was introduced in 1.8 in Rancher Desktop Agent, where If Kubernetes sends updates for services and the port mappings had not changed, the existing maps are deleted.

Other changes

There are no other new features in this release (compared to 1.8.1).

The default window size of the application has been increased.

There are some bug fixes related to deployment profiles and the first-run dialog.

Updates to bundled utilities

• helm 3.11.2 → 3.11.3
• docker 23.0.1 → 23.0.3
• docker-compose 2.16.0 → 2.17.2
• nerdctl 1.2.1 → 1.3.0
• trivy 0.38.2 → 0.39.1

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.8.1, can be found using GitHub compare and the details of the release can be found in the v1.9.0-tech-preview milestone.

This is the 1.8.1 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to Mac, Windows, and Linux.

Installers

• Windows
• macOS x86_64
• macOS aarch64
• Linux install notes

This patch release fixes one issue in Rancher Desktop 1.8.0

The new experimental deployment profile functionality was broken on Windows. This has been fixed.

There are no other changes in this release compared to 1.8.0

Please check the Rancher Desktop 1.8.0 release notes for a comprehensive list of new features and bug fixes.

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.8.0, can be found using GitHub compare and the details of the release can be found in the v1.8.1 milestone.

This is the 1.8.0 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to Mac, Windows, and Linux.

Installers

• Windows
• macOS x86_64
• macOS aarch64
• Linux install notes

New Features

Configurable application behavior, e.g. auto-start at login

Some aspects of application behavior can now be configured via the Application | Behavior preferences:

• Automatically start at login
• Start in the background
• Quit when closing the application window
• Hide notification icon

All application settings can be changed via rdctl

Both rdctl start and rdctl set can be used to pass values for any configuration setting except

• diagnostics.showMuted
• WSL.integration

Use rdctl set --help to get list of settings supported on the current platform.

Deployment profile (experimental)

Deployment profiles can be used both by the user and by administrators to provide initial preference settings on first-run (or after a factory-reset), and to lock down settings, so they cannot be changed via the GUI or CLI.

New networking stack on Windows (experimental)

An experimental network stack on Windows should provide better compatibility with various VPN configurations. It also uses its own network namespace, providing better isolation from other WSL2 distros on the same machine. It is still a work-in-progress (port forwarding has to be performed manually) and has some limitations (WSL integration is not yet implemented). Please read the documentation section in the Epic to see how to enable and use it. Please provide feedback if you run into any problems beyond the documented limitations.

Support for Apple Virtualization framework on macOS (experimental)

On macOS, it is now possible to use experimental support for the Virtualization framework instead of QEMU for running the virtual machine. Unlike QEMU it supports more than 8 CPUs on aarch64 machines. There are several known performance and stability issues, so this is for evaluation purposes only. Virtual machine type can be switched with from QEMU to VZ with

rdctl set --virtual-machine.type vz

Important Bug fixes and enhancements

Kubernetes 1.26 and Moby

Kubernetes 1.26 now works again with both container engines.

Additional mount points on macOS

On macOS, the directories /Volumes and /var/folders are automatically mounted into the VM, so any directories under them can be bound into containers. This includes the $TMPDIR directory.

Kubernetes ingress binding to 0.0.0.0 on Windows

On Windows, the Kubernetes loadbalancer services are now bound to all interfaces, so they can be accessed from other machines on the local network (just like on macOS). The old behavior (binding only to 127.0.0.1) can be restored with

rdctl set --kubernetes.ingress.localhost-only true

This cannot yet be configured via the GUI.

socket_vmnet has been updated on macOS (experimental)

socket_vmnet is going to be the replacement for the current vde_vmnet driver that is responsible for creating routable IP addresses (requires running with "administrative access"). There have been several bug fixes to socket_vmnet. Select it with:

rdctl set --experimental.virtual-machine.socket-fmnet=true

File sharing via 9p on macOS (experimental)

On macOS, the alternate filesystem protocol 9p can now be selected via rdctl instead of creating a Lima override.yaml file

rdctl set--experimental.virtual-machine.mount.type 9p

9p mount options can also be configured; they will apply to all mounted volumes:

--experimental.virtual-machine.mount.9p.cache-mode string         (Allowed values: [none, loose, fscache, mmap])
--experimental.virtual-machine.mount.9p.msize-in-kb int           maximum packet size
--experimental.virtual-machine.mount.9p.protocol-version string   (Allowed values: [9p2000, 9p2000.u, 9p2000.L])
--experimental.virtual-machine.mount.9p.security-model string     (Allowed values: [passthrough, mapped-xattr, mapped-file, none])

Known issues

Experimental features can only be configured via rdctl

They are not exposed via the Preferences dialog yet.

Allowed Images

When the Allowed Images list is enabled, all images from *.pkg.dev (the Google CDN) are implicitly allowed to enable pulling from Google Cloud registries.

The format used to specify image patterns is still subject to change.

Long time to shut down Rancher Desktop when using the Virtualization framework

Due to a bug in the bindings, there is a "panic" in the shutdown of the VM (also visible in the logs), which will take an additional 3 minutes to time out.

Experimental Features

The following features are considered "experimental" and may change in incompatible ways (or be removed) without advance notice:

rdctl commandline syntax

If changes are made, the old syntax will continue to be supported if possible, but this cannot be guaranteed.

The output of rdctl command may also change in the future. E.g. rdctl list-settings currently just dumps out the settings object in JSON format, but could provide a better organized / readable format in the future.

API

The Rancher Desktop backend provides an API that is used both by the GUI frontend and by rdctl, and can also be used directly via rdctl api. The API is versioned, but the version might change without prior notice, and backward compatibility should not be expected.

Allowed Images

The allowed image list is still considered experimental, mostly because the pattern format is still going to change from extended regular expressions (intentionally under-documented) to simple wildcard matches.

New networking stack

The new networking stack implementation is still ongoing. It is not yet a full implementation on Windows, and not yet available on Linux and macOS at all.

Filesharing via 9p on macOS

socket_vmnet networking driver on macOS

Virtualization framework on macOS

This configuration is still considered experimental in the Lima project, which Rancher Desktop uses on macOS to implement the virtual machine. There are various known performance and stability problems that have to be resolved upstream.

Deprecated Features

This section provides a warning about features that will become unsupported in the future.

Catalina

Support for macOS Catalina will be removed in Rancher Desktop 1.10.

Kubernetes 1.24.1 to 1.24.3 with Moby engine

Kubernetes 1.24.1 to 1.24.3 will no longer work with the moby engine in Rancher Desktop 1.10. They will continue to work with containerd. Kubernetes 1.24.4 and later will continue to be supported with moby.

Removed Features

No features have been removed in this release

Updates to bundled utilities

• docker 20.10.21 → 23.0.1
• docker-buildx 0.9.1 → 0.10.4
• docker-compose 2.14.0 → 2.16.0
• helm 3.10.2 → 3.11.2
• nerdctl 1.0.0. → 1.2.1
• trivy 0.35.0 → 0.38.3

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.7.0, can be found using GitHub compare and the details of the release can be found in the v1.8.0 milestone.

This is the 1.7.0 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to Mac, Windows, and Linux.

Important Updates

New Windows MSI installer

This allows enterprise rollout using group policy, or other system management systems. Work is still ongoing to make the MSI installer more configurable in the following releases, so that the initial Rancher Desktop configuration can be specified during install as well.

Allowed Images (Experimental)

The Allowed Images list lets the user control which images can be pulled from (and pushed to) registries. The images are configured via patterns in the Container Runtime preferences dialog. This is not a security barrier, but helps to conform to local policy, e.g. to prevent a helm install from pulling images from an unexpected source. Read more in the docs.

Please report any problems pulling (or pushing) images while the Allowed Images list is enabled as GitHub issues.

Reclaim unused space (macOS only)

On macOS, any unused disk space in the data volume (e.g. from deleted images) will be returned to the host when the application is closed.

Use compressed k3s images

For Kubernetes 1.21 and later, Rancher Desktop will now download (and cache) compressed image tarballs (e.g. 160MB instead of 470MB per version). It will continue to use uncompressed images already in the cache to avoid downloading them again unless you do a factory reset and delete all cached images.

Other updates and fixes

Help buttons in Preferences dialog

The Preferences dialog pages now have a help button (question mark in a circle) that will link directly to the corresponding manual page.

The online documentation is now versioned, so any links from the app will always go to the corresponding version of the documentation.

rdctl factory-reset

It is now possible to run a factory reset from the command line even when Rancher Desktop isn't running, so it can be used to clean up a broken installation that won't even start.

Updated Utilities

• docker 20.10.17 → 20.10.21
• docker-compose 2.11.1 → 2.14.0
• helm 3.9.4 → 3.10.2
• nerdctl 0.23.0 → 1.0.0
• trivy 0.32.0 → 0.35.0

Known Issues

Downgrading from 1.7

Downgrading from Rancher Desktop 1.7.0 to previous releases requires a factory reset (as usual) with the "Keep all cached images" option disabled because previous versions don't work correctly when they encounter compressed image tarballs in the cache. Details are in the FAQ.

On Windows, it is also possible that the privileged helper process needs to be uninstalled manually; see the docs for more details.

Kubernetes 1.26

Kubernetes 1.26 is only supported with the containerd engine in this release. Use Kubernetes 1.25 or earlier if you need to use the docker socket with the moby engine.

Allowed Images

When the Allowed Images list is enabled, all images from *.pkg.dev (the Google CDN) are implicitly allowed to enable pulling from Google Cloud registries.

The format used to specify image patterns is still subject to change.

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.6.2, can be found using GitHub compare and the details of the release can be found in the v1.7.0 milestone.

This is the 1.6.2 release of Rancher Desktop, an open source desktop application to bring Kubernetes and container management to Mac, Windows, and Linux.

This patch release fixes an incompatibility with macOS Ventura

Rancher Desktop 1.6.0 and 1.6.1 do not work properly with macOS 13 Ventura. When running Kubernetes versions 1.24.* or 1.25.*, the VM would hang right away before becoming ready. With earlier versions, Kubernetes would work initially, but start hanging after restarting Rancher Desktop. This issue has been fixed.

There are no other changes in this release compared to 1.6.1.

Connect with the developers

• The issue queue

• Rancher Users Slack in the #rancher-desktop channel

Changelog

The full version changelog, from v1.6.1, can be found using GitHub compare and the details of the release can be found in the v1.6.2 milestone.