What happened?
Using Rancher Desktop 1.22 on Macos configured with docker engine (docker API) and the containerd storage driver, sudo vcluster create vc1 hangs waiting for the vCluster to be available:
08:37:14 info Starting vCluster standalone vc1
08:37:14 debug Running command: docker exec vcluster.cp.vc1 bash -c set -e -o pipefail; curl -sfLk "https://github.com/loft-sh/vcluster/releases/download/v0.32.1/install-standalone.sh" | sh -s -- --skip-download --skip-wait --vcluster-name vc1 --join-token dabadaba
08:37:15 info 🔄 Setting up persistent logging...
08:37:15 info ✅ systemd-journald restarted.
08:37:15 info 🔄 Creating vCluster systemd service...
08:37:15 info 🔄 Creating systemd service file /etc/systemd/system/vcluster.service
08:37:15 info ✅ vcluster.service created.
08:37:15 info 🔄 Starting vcluster.service...
08:37:15 info Created symlink /etc/systemd/system/multi-user.target.wants/vcluster.service → /etc/systemd/system/vcluster.service.
08:37:16 info ✅ Successfully started vcluster.service
08:37:16 done Successfully created virtual cluster vc1
08:37:16 info Finding docker container vcluster.cp.vc1...
08:37:16 debug Found exposed port 10383 for vcluster container vcluster.cp.vc1
08:37:16 info Waiting for vCluster kubeconfig to be available...
08:37:16 debug Kubeconfig not yet available: exit status 1
08:37:24 info Waiting for vCluster to become ready...
08:37:34 debug vCluster not ready yet: client rate limiter Wait returned an error: context deadline exceeded - error from a previous attempt: EOF
08:40:25 fatal failed connecting to vcluster: timeout waiting for vcluster to become ready: context deadline exceeded
What did you expect to happen?
Readiness
How can we reproduce it (as minimally and precisely as possible)?
See "What happened"
vCluster config
Details
vCluster and Docker version
Details
$ vcluster --version
version: 0.32.1
os: darwin
arch: arm64
$ docker version
Client:
Version: 29.1.4-rd
API version: 1.52
Go version: go1.25.5
Git commit: 3c6914c
Built: Fri Jan 9 20:45:44 2026
OS/Arch: darwin/arm64
Context: rancher-desktop
Server:
Engine:
Version: 29.1.3
API version: 1.52 (minimum version 1.41)
Go version: go1.25.5
Git commit: fbf3ed25f893e6ce21336f1101590e40a13934f4
Built: Sun Dec 14 05:31:58 2025
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: v2.2.0
GitCommit: 1c4457e00facac03ce1d75f7b6777a7a851e5c41
runc:
Version: 1.4.0
GitCommit: 8bd78a9977e604c4d5f67a7415d7b8b8c109cdc4
docker-init:
Version: 0.19.0
GitCommit:
$ uname -a
Darwin XLTH-42TDWV-JB 25.3.0 Darwin Kernel Version 25.3.0: Wed Jan 28 20:54:46 PST 2026; root:xnu-12377.91.3~2/RELEASE_ARM64_T6000 arm64
Operating System
macOS (Apple Silicon)
Using vCluster Platform UI?
No - not using Platform UI
Relevant logs
Anything else we need to know?
non-sudo create also hangs with Rancher Desktop's docker host.
In addition, vcluster create also hung at the same point using (1) podman desktop and (2) socktainer as docker host.
What happened?
Using Rancher Desktop 1.22 on Macos configured with docker engine (docker API) and the containerd storage driver,
sudo vcluster create vc1hangs waiting for the vCluster to be available:What did you expect to happen?
Readiness
How can we reproduce it (as minimally and precisely as possible)?
See "What happened"
vCluster config
Details
vCluster and Docker version
Details
Operating System
macOS (Apple Silicon)
Using vCluster Platform UI?
No - not using Platform UI
Relevant logs
Anything else we need to know?
non-sudo create also hangs with Rancher Desktop's docker host.
In addition, vcluster create also hung at the same point using (1) podman desktop and (2) socktainer as docker host.