Keep getting error runing colima FATA[0001] error starting vm: error at 'starting': exit status 1

[joshboyye]

Description

I downloaded the Colima but I wanted to run it however it keeps showingFATA[0001] error starting vm: error at 'starting': exit status 1 like this so I don't know how to solve the problem. Please help me

Version

Colima Version: Lima Version: Qemu Version:

Operating System

• [ ] macOS Intel
• [X] macOS M1
• [ ] Linux

Reproduction Steps

Expected behaviour

No response

Additional context

No response

[abiosoft]

Kindly fill the issue template and share the output of colima start --verbose

[joshboyye]

It still doesn't work

[abiosoft]

I suspect you're running and x86_64 version of Qemu on your M1 device. Can you kindly confirm if your HomeBrew installation is for M1 and not Intel?

[joshboyye]

yes the homebrew is installed on my computer

[abiosoft]

Can you share the output of /Users/joshuawang/.lima/colima/ha.stderr.log?

cat /Users/joshuawang/.lima/colima/ha.stderr.log

FYI, it is better to copy the text directly than share a screenshot.

[joshboyye]

how do I share the directly?

[arditarapi]

Facing the same issue here {"level":"debug","msg":"Creating iso file /Users/adm/.lima/colima/cidata.iso","time":"2022-12-20T16:57:28+01:00"} {"level":"debug","msg":"Using /var/folders/v8/fqwl_nqj39vg0g9gyjmg7x2w0000gn/T/diskfs_iso310208009 as workspace","time":"2022-12-20T16:57:28+01:00"} {"level":"debug","msg":"OpenSSH version 9.0.1 detected","time":"2022-12-20T16:57:28+01:00"} {"level":"debug","msg":"AES accelerator seems available, prioritizing [email protected] and [email protected]","time":"2022-12-20T16:57:28+01:00"} {"level":"info","msg":"Starting VZ (hint: to watch the boot progress, see \"/Users/adm/.lima/colima/serial.log\")","time":"2022-12-20T16:57:28+01:00"} {"level":"debug","msg":"Start tcp server listening on: 127.0.0.1:64429","time":"2022-12-20T16:57:28+01:00"} {"level":"debug","msg":"Start udp server listening on: 127.0.0.1:57371","time":"2022-12-20T16:57:28+01:00"} {"level":"debug","msg":"[VZ] - vm state change: \"VirtualMachineStateStarting\"","time":"2022-12-20T16:57:28+01:00"} {"level":"info","msg":"new connection from to ","time":"2022-12-20T16:57:28+01:00"} {"level":"info","msg":"[VZ] - vm state change: running","time":"2022-12-20T16:57:28+01:00"} {"level":"info","msg":"Waiting for the essential requirement 1 of 3: \"ssh\"","time":"2022-12-20T16:57:28+01:00"} {"level":"debug","msg":"executing script \"ssh\"","time":"2022-12-20T16:57:28+01:00"} {"level":"debug","msg":"executing ssh for script \"ssh\": /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/Users/adm/.lima/_config/user\" -o IdentityFile=\"/Users/adm/.ssh/id_ed25519\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^[email protected],[email protected]\" -o User=adm -o ControlMaster=auto -o ControlPath=\"/Users/adm/.lima/colima/ssh.sock\" -o ControlPersist=5m -p 64428 127.0.0.1 -- /bin/bash]","time":"2022-12-20T16:57:28+01:00"} {"level":"info","msg":"[VZ] - vm state change: stopped","time":"2022-12-20T16:57:29+01:00"} {"level":"info","msg":"Driver stopped due to error: \"vz driver state stopped\"","time":"2022-12-20T16:57:29+01:00"} {"level":"info","msg":"Shutting down the host agent","time":"2022-12-20T16:57:29+01:00"} {"level":"debug","msg":"shutting down the SSH master","time":"2022-12-20T16:57:29+01:00"} {"level":"debug","msg":"executing ssh for exiting the master: /usr/bin/ssh [ssh -F /dev/null -o IdentityFile=\"/Users/adm/.lima/_config/user\" -o IdentityFile=\"/Users/adm/.ssh/id_ed25519\" -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o NoHostAuthenticationForLocalhost=yes -o GSSAPIAuthentication=no -o PreferredAuthentications=publickey -o Compression=no -o BatchMode=yes -o IdentitiesOnly=yes -o Ciphers=\"^[email protected],[email protected]\" -o User=adm -o ControlMaster=auto -o ControlPath=\"/Users/adm/.lima/colima/ssh.sock\" -o ControlPersist=5m -O exit -p 64428 127.0.0.1]","time":"2022-12-20T16:57:29+01:00"} {"error":"failed to execute ssh -O exit -p 64428 127.0.0.1, out=\"Control socket connect(/Users/adm/.lima/colima/ssh.sock): No such file or directory\\r\\n\": exit status 255","level":"warning","msg":"failed to exit SSH master","time":"2022-12-20T16:57:29+01:00"} {"level":"info","msg":"Shutting down VZ","time":"2022-12-20T16:57:29+01:00"}

[abiosoft]

@arditarapi what OS are you on? And what is the output of colima list?

Does qemu work better?

colima start --vm-type qemu

[arditarapi]

I am on Ventura 13.1 (22C65) colima list default Running aarch64 2 2GiB 60GiB docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. colima start --vm-type qemu its the same

[pengisgood]

When I run colima start on macbookpro (11.5.2，with intel chip) for the first time, I got the following error:

INFO[0000] starting colima
INFO[0000] starting ...                                  context=vm
> msg="Using the existing instance \"colima\""
> msg="Attempting to download the image from \"https://cloud-images.ubuntu.com/impish/current/impish-server-cloudimg-amd64.img\"" digest=
> msg="failed to download the image, attempted 2 candidates, errors=[failed to download \"https://cloud-images.ubuntu.com/impish/current/impish-server-cloudimg-
FATA[0000] error starting vm: error at 'starting': exit status 1

[abiosoft]

@pengisgood you are either running a very old version of Colima or you have Lima overrides enabled.

What is the output of colima version?

[pengisgood]

colima version 0.2.2

[abiosoft]

@pengisgood that is too old and no longer supported. Kindly updated to a more recent version.

[pengisgood]

@abiosoft

After I upgraded to 0.5.0, stuck with [hostagent] Waiting for the essential requirement 1 of 5: "ssh" after run colima start

colima start debug

INFO[0000] starting colima [profile=debug] INFO[0000] runtime: docker INFO[0000] preparing network ... context=vm INFO[0000] creating and starting ... context=vm [hostagent] Waiting for the essential requirement 1 of 5: "ssh" [hostagent] Waiting for the essential requirement 1 of 5: "ssh" [hostagent] Waiting for the essential requirement 1 of 5: "ssh" [hostagent] Waiting for the essential requirement 1 of 5: "ssh" [hostagent] Waiting for the essential requirement 1 of 5: "ssh" [hostagent] Waiting for the essential requirement 1 of 5: "ssh"

[abiosoft]

@pengisgood seems your Mac is finding it difficult to use the macOS virtualisation. Kindly upgrade to v0.5.2 or fall back to Qemu with --vm-type qemu

[pengisgood]

@abiosoft

upgraded to 0.5.2

colima start

INFO[0000] starting colima INFO[0000] runtime: docker INFO[0000] preparing network ... context=vm INFO[0000] creating and starting ... context=vm Terminal is not available, proceeding without opening an editor field dns must be empty when field useHostResolver is true FATA[0000] error starting vm: error at 'creating and starting': exit status 1

[abiosoft]

@pengisgood kindly do a reset.

colima delete
colima start

[pengisgood]

@abiosoft

@pengisgood kindly do a reset.

colima delete
colima start

still the same error

[abiosoft]

@pengisgood you still getting useHostResolver error or the [hostagent] Waiting for the essential requirement 1 of 5: "ssh" error ?

[phyrog]

@abiosoft

upgraded to 0.5.2

colima start

INFO[0000] starting colima INFO[0000] runtime: docker INFO[0000] preparing network ... context=vm INFO[0000] creating and starting ... context=vm Terminal is not available, proceeding without opening an editor field dns must be empty when field useHostResolver is true FATA[0000] error starting vm: error at 'creating and starting': exit status 1

I was getting the same issue today. For me it turned out to be an old version of limactl that was conflicting with colima. After uninstalling the old version, it worked for me.

[amilkareslava]

@phyrog what version of limact do you have?

[phyrog]

@amilkareslava I had 0.9.2. Now I have 0.14.2

[pengisgood]

@abiosoft After upgraded limactl to 0.14.2, it works.

[Nakilon]

Right after brew install colima:

$ colima start
INFO[0000] starting colima                              
INFO[0000] creating and starting ...                     context=vm
> msg="Terminal is not available, proceeding without opening an editor"
> msg="Attempting to download the image from \"https://cloud-images.ubuntu.com/impish/current/impish-s
> msg="failed to download the image, attempted 2 candidates, errors=[failed to download \"https://clou
FATA[0001] error starting vm: error at 'creating and starting': exit status 1

$ colima version
colima version 0.2.2
git commit: b2c7697bee2d73e995f156fe8e9870eb246c07e6

$ sw_vers
ProductName:	macOS
ProductVersion:	11.4
BuildVersion:	20F71

[cmcneese]

I just recently in the past few days started having this issue. I'm not sure if it was something I updated or what has changed. Happy to provide any and all info that may help. I have an M1 mac for work, that I haven't noticed the issue on yet, so I may hold off on updating. I've noticed this an issue on my Intel-2020 MBP though.

qemu-img version 8.1.0 colima version 0.5.5 limactl version 0.17.2 x86_64

[rfay]

In the latest version this is a duplicate of

• https://github.com/abiosoft/colima/issues/777#issuecomment-1694654255

(and several others).

There has been an enormous amount of drama on this over the last couple of weeks, as far as I understand it affected Intel/amd64 only, and it should be sorted out (again) now.

[cmcneese]

I understand if it is a duplicate, just wanted to share as I have been pouring over the boards trying to resolve my issue too. Not trying to bring drama, just wanting to figure out what has affected the x86 version. I can confirm that everything is working fine for me on my M1.

I'll check the link you shared. Thank you!

[Nakilon]

This can't be a 'duplicate' because it's older. That can be a 'duplicate' or a 'blocker' of this one.

[rickvian]

@arditarapi what OS are you on? And what is the output of colima list?

Does qemu work better?

colima start --vm-type qemu

Thanks, i face issue where my colima start show error

FATA[0001] error starting vm: error at 'starting': exit status 1 

with colima list it shows this:

PROFILE    STATUS    ARCH       CPUS    MEMORY    DISK     RUNTIME    ADDRESS
default    Broken    aarch64    4       8GiB      60GiB     

then i search in the readme,

https://github.com/abiosoft/colima/blob/main/docs/FAQ.md#broken-status

after i do

colima stop --force

then i do

colima start

it worked again, thanks for the hint!

[afrijaldz]

@arditarapi what OS are you on? And what is the output of colima list? Does qemu work better?

colima start --vm-type qemu

Thanks, i face issue where my colima start show error

FATA[0001] error starting vm: error at 'starting': exit status 1 

with colima list it shows this:

PROFILE    STATUS    ARCH       CPUS    MEMORY    DISK     RUNTIME    ADDRESS
default    Broken    aarch64    4       8GiB      60GiB     

then i search in the readme,

https://github.com/abiosoft/colima/blob/main/docs/FAQ.md#broken-status

after i do

colima stop --force

then i do

colima start

it worked again, thanks for the hint!

thanks, this works for me