-
-
Notifications
You must be signed in to change notification settings - Fork 508
Open
Description
Description
I am trying to use colima+docker on macOS. I have created a new standard user with which I intend to run docker containers.
When starting colima with this user, the startup hangs at Waiting for the essential requirement 1 of 3: "ssh"
I do not have this issue with the administrator account on which brew install colima was run. More importantly, I do not have the issue either with another standard user I've been using for a while.
% colima start -v
INFO[0000] starting colima
INFO[0000] runtime: docker
INFO[0001] creating and starting ... context=vm
> Terminal is not available, proceeding without opening an editor
> Starting the instance "colima" with internal VM driver "vz"
> "Attempting to download the image" arch=aarch64 digest= location=/Users/docker/Library/Caches/colima/caches/a837ead25fc8b5a51db8347e9b28f7a46aadc1f99d4a8f133e6e5057c4efc46f
> Downloaded the image from "/Users/docker/Library/Caches/colima/caches/a837ead25fc8b5a51db8347e9b28f7a46aadc1f99d4a8f133e6e5057c4efc46f"
> Converting "/Users/docker/.colima/_lima/colima/basedisk" (qcow2) to a raw disk "/Users/docker/.colima/_lima/colima/diffdisk"
> Expanding to 20GiB
> [hostagent] hostagent socket created at /Users/docker/.colima/_lima/colima/ha.sock
> [hostagent] Starting VZ (hint: to watch the boot progress, see "/Users/docker/.colima/_lima/colima/serial*.log")
> [hostagent] Mounting disk "colima" on "/mnt/lima-colima"
> [hostagent] Converting "/Users/docker/.colima/_lima/_disks/colima/datadisk" (raw) to a raw disk "/Users/docker/.colima/_lima/_disks/colima/datadisk"
> [hostagent] [VZ] - vm state change: running
> [hostagent] SSH server does not seem to be running on vsock port, using usernet forwarder
> SSH Local Port: 49195
> [hostagent] Waiting for the essential requirement 1 of 3: "ssh"
Version
colima version 0.9.1
git commit: 0cbf719f5409ce04b9f0607b681c005d2ff7d94a
limactl version 2.0.2
zsh: command not found: qemu-img
Operating System
- macOS Intel <= 13 (Ventura)
- macOS Intel >= 14 (Sonoma)
- Apple Silicon <= 13 (Ventura)
- Apple Silicon >= 14 (Sonoma)
- Linux
Output of colima status
On the failing user, I get
% colima status
FATA[0000] error retrieving current runtime: empty value
On other users, I have
% colima status
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] docker socket: unix:///Users/me/.colima/default/docker.sock
INFO[0000] containerd socket: unix:///Users/me/.colima/default/containerd.sock
Reproduction Steps
- With an administrator account, run
brew install dockerandbrew install colima - Create a new standard user
- With this user, run
colima start
Expected behaviour
The documentation should specify the needed configuration needed for a new account to be able to run colima. I am unable to pinpoint the config difference between the failing account and the others.
Additional context
No response
Metadata
Metadata
Assignees
Labels
No labels