Skip to content

Add support for Rancher Desktop - #251

Merged
psviderski merged 1 commit into
psviderski:mainfrom
mitio:main
Feb 15, 2026
Merged

psviderski merged 1 commit into
psviderski:mainfrom
mitio:main

Conversation

@mitio

@mitio mitio commented Feb 13, 2026

Copy link
Copy Markdown
Contributor

Rancher Desktop is a free alternative to Docker Desktop (which prohibits commercial use) and has gained significant popularity. When running Rancher Desktop on non-native Docker platforms such as macOS and Windows, the secondary tunnel from the host OS to the Docker's Linux machine is necessary. At the moment, the check for this seems to be based on the vhost name of the docker engine's VM.

For Rancher Desktop it seemms to be lima-rancher-desktop:

$ docker info --format 'json' | jq .Name
"lima-rancher-desktop"

This might not be the best approach but is simple and should save a lot of headaches for a lot of people until a potentially better solution is devised.

See also: psviderski/unregistry#62

Rancher Desktop is a free alternative to Docker Desktop (which prohibits
commercial use) and has gained significant popularity. When running
Rancher Desktop on non-native Docker platforms such as macOS and
Windows, the secondary tunnel from the host OS to the Docker's Linux
machine is necessary. At the moment, the check for this seems to be
based on the vhost name of the docker engine's VM.

For Rancher Desktop it seemms to be `lima-rancher-desktop`:

  $ docker info --format 'json' | jq .Name

This might not be the best approach but is simple and should save a lot
of headaches for a lot of people until a potentially better solution is
devised.

See also: psviderski/unregistry#62
@jabr

jabr commented Feb 14, 2026 •

Copy link
Copy Markdown
Contributor

I'm not entirely clear on when this comes up (when using your laptop/desktop as a machine?), but do we want to also include orbstack if we're adding to this list? It's another alternative to Docker Desktop like Rancher. Any others to include?

$ docker info --format json | jq .Name
"orbstack"

@mitio

mitio commented Feb 15, 2026

Copy link
Copy Markdown
Contributor Author

@jabr apologies for not providing enough context.

This happens when I try e.g. uc deploy from my dev machine (macOS) that runs Rancher Desktop, to an uncloud cluster/machine that might be running Linux. What matters is the source, i.e. my dev machine, as this is where images are built and deployed from.

This thead and specifically this comment have a bit more context on potential alternative solutions.

@psviderski psviderski left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for fix!

As discussed in the unregistry issue psviderski/unregistry#13 (comment), I think always running a proxy on macOS is a good idea. I already implemented it for unregistry: psviderski/unregistry@7205fb1 and will create a follow-up for uncloud as well.

However, it's still good to have this check as a fallback when using Linux with a virtualised Docker locally.

@psviderski
psviderski merged commit d3ee739 into psviderski:main Feb 15, 2026
3 of 4 checks passed
v3rmine pushed a commit to v3rmine/uncloud that referenced this pull request Mar 5, 2026
…i#251)

Rancher Desktop is a free alternative to Docker Desktop (which prohibits
commercial use) and has gained significant popularity. When running
Rancher Desktop on non-native Docker platforms such as macOS and
Windows, the secondary tunnel from the host OS to the Docker's Linux
machine is necessary. At the moment, the check for this seems to be
based on the vhost name of the docker engine's VM.

For Rancher Desktop it seemms to be `lima-rancher-desktop`:

  $ docker info --format 'json' | jq .Name

This might not be the best approach but is simple and should save a lot
of headaches for a lot of people until a potentially better solution is
devised.

See also: psviderski/unregistry#62
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants