Colima unable to restart on m1 after operating system restart #381

jamie-smyth-at-thistle · 2022-07-29T18:50:43Z

Description

We are seeing an issue where colima will not restart after OS X shuts down if colima is running during shutdown.

➜  ~ colima start --verbose
INFO[0000] using docker runtime
INFO[0000] starting colima
INFO[0000] starting ...                                  context=vm
> msg="Using the existing instance \"colima\""
> msg="errors inspecting instance: [failed to get Info from \"/Users/dipdhanesha/.lima/colima/ha.sock\": Get \"http:https://lima-hostagent/v1/info\": dial unix /Users/dipdhanesha/.lima/colima/ha.sock: connect: connection refused]"
FATA[0000] error starting vm: error at 'starting': exit status 1

Version

Colima Version:

➜  ~ colima version
colima version 0.3.4
git commit: 5a4a70481ca8d1e794677f22524e3c1b79a9b4ae

Lima Version:

➜  ~ limactl --version
limactl version 0.10.0

Qemu Version:

➜  ~ qemu-img --version
qemu-img version 6.2.0
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers

Operating System

macOS Intel
macOS M1
Linux

Reproduction Steps

colima start
Shutdown Mac OS (without running colima stop)
Start Mac OS
colima start

Expected behaviour

Colima starts successfully

Additional context

No response

The text was updated successfully, but these errors were encountered:

abiosoft · 2022-07-29T20:18:25Z

What is the output of colima list?

Does deleting the socket file has any effect? i.e. delete and try again.

rm /Users/dipdhanesha/.lima/colima/ha.sock
colima start

jamie-smyth-at-thistle · 2022-07-29T21:56:48Z

Thanks for the quick response. I will need to get it back into the broken state and try deleting the sock file. Had to delete and recreate colima to get some work done. Hopefully I can get back to you shortly.

dip-thistle · 2022-08-01T16:50:35Z

Hi @abiosoft, This is the output of colima list

➜  ~ colima list
PROFILE    STATUS    ARCH       CPUS    MEMORY    DISK
default    Broken    aarch64    6       8GiB      60GiB

I removed the socket file and tried running the command again but it did not work. This was the output.

➜  ~ rm /Users/dipdhanesha/.lima/colima/ha.sock
➜  ~ colima start
INFO[0000] using docker runtime
INFO[0000] starting colima
INFO[0000] starting ...                                  context=vm
> msg="Using the existing instance \"colima\""
> msg="errors inspecting instance: [failed to connect to \"/Users/dipdhanesha/.lima/colima/ha.sock\": stat /Users/dipdhanesha/.lima/colima/ha.sock: no such file or directory]"
FATA[0000] error starting vm: error at 'starting': exit status 1

abiosoft · 2022-08-01T16:51:50Z

Thanks for the update, will have a look.

Jsince99 · 2022-08-23T05:21:22Z

Hey, @abiosoft , and @dip-thistle
I had the same issue. I tried stopping broken instance and started it again it worked.

limactl stop -f colima

INFO[0000] The QEMU process seems already stopped       
INFO[0000] Sending SIGKILL to the host agent process 1689 
ERRO[0000] operation not permitted                      
INFO[0000] Removing *.pid *.sock under "/Users/sravanth/.lima/colima" 
INFO[0000] Removing "/Users/sravanth/.lima/colima/ga.sock" 
INFO[0000] Removing "/Users/sravanth/.lima/colima/ha.pid" 
INFO[0000] Removing "/Users/sravanth/.lima/colima/ha.sock"

colima start

INFO[0000] starting colima                              
INFO[0000] runtime: docker                              
INFO[0000] preparing network ...                         context=vm
INFO[0001] starting ...                                  context=vm
INFO[0023] provisioning ...                              context=docker
INFO[0023] starting ...                                  context=docker
INFO[0029] done

abiosoft · 2022-08-23T05:23:49Z

limactl stop -f colima

This is equivalent to colima stop -f

Jerome1337 · 2022-11-21T09:13:21Z

I had the same issue on 2019 Intel Macbook Pro after a OS restart.

The error was:

> errors inspecting instance: [failed to get Info from "/Users/JEROME/.lima/colima/ha.sock": Get "http:https://lima-hostagent/v1/info": dial unix /Users/JEROME/.lima/colima/ha.sock: connect: connection refused]

After executing colima stop -f everything was ok

Agnibho-8 · 2023-01-24T05:24:30Z

Colima stop didn't work,
instead system restart worked for me

abiosoft · 2023-01-24T05:55:12Z

Colima stop didn't work, instead system restart worked for me

You can use the `--force` flag to enforce it when `stop` fails. ``` colima stop --force ```

dehengxu · 2023-03-29T05:47:28Z

Hi @abiosoft, This is the output of colima list

➜  ~ colima list
PROFILE    STATUS    ARCH       CPUS    MEMORY    DISK
default    Broken    aarch64    6       8GiB      60GiB

I removed the socket file and tried running the command again but it did not work. This was the output.

➜  ~ rm /Users/dipdhanesha/.lima/colima/ha.sock
➜  ~ colima start
INFO[0000] using docker runtime
INFO[0000] starting colima
INFO[0000] starting ...                                  context=vm
> msg="Using the existing instance \"colima\""
> msg="errors inspecting instance: [failed to connect to \"/Users/dipdhanesha/.lima/colima/ha.sock\": stat /Users/dipdhanesha/.lima/colima/ha.sock: no such file or directory]"
FATA[0000] error starting vm: error at 'starting': exit status 1

Try to delete ha.pid

davidkyles · 2023-04-27T16:47:38Z

Thank you. deleting ha.sock, ha.pid and vz.pid got me back up and running

davepoon · 2023-05-03T06:03:35Z

As a developer using a m1 Mac, I experience this issue on a daily basis while working with nodejs and php containers. I hope a solution can be found without the need for frequent restarts.

protometa · 2023-09-26T20:12:56Z

a colima restart -f also fixed it for me

joachim-n · 2023-10-03T08:25:21Z

I can confirm that limactl stop -f colima fixed it for me.

But I have been shutting down my mac every day with colima still running, and today is the first time I've had this problem.

skgandikota · 2023-10-22T06:38:51Z

limactl stop -f colimaworked for me.

drupalninja · 2023-12-12T13:25:59Z

limactl stop -f colima

this worked for me thanks!

farooqkhanDH · 2024-01-02T16:56:38Z

Force stopping using colima stop -f and starting again worked for me.

laacpleesis · 2024-01-09T09:18:01Z

Restarting my mac and colima did not solve the issue. It was still stuck on

msg="errors inspecting instance: [failed to get Info from "/Users/USER/.lima/colima/ha.sock": Get "http:https://lima-hostagent/v1/info": dial unix /Users/USER/.lima/colima/ha.sock: connect: connection refused]"

and inside logs (cat /Users/USER/.colima/_lima/colima/ha.stderr.log):

{"level":"fatal","msg":"template: :1:21: executing "" at \u003cfd_connect "/Users/USER/.colima/_lima/_networks/user-v2/user-v2_qemu.sock"\u003e: error calling fd_connect: fd_connect: dial unix /Users/USER/.colima/_lima/_networks/user-v2/user-v2_qemu.sock: connect: connection refused","time":"2024-01-09T10:45:32+02:00"}

And reinstalling lima and qemu didnt help. I then tried

chmod +x /Users/USER/.colima/_lima/_networks/user-v2/user-v2_qemu.sock

still same error.

then I tried

rm /Users/USER/.colima/_lima/_networks/user-v2/user-v2_qemu.sock

and inside logs (cat /Users/USER/.colima/_lima/colima/ha.stderr.log):

{"level":"fatal","msg":"template: :1:21: executing "" at \u003cfd_connect "/Users/USER/.colima/_lima/_networks/user-v2/user-v2_qemu.sock"\u003e: error calling fd_connect: fd_connect: dial unix /Users/USER/.colima/_lima/_networks/user-v2/user-v2_qemu.sock: connect: no such file or directory","time":"2024-01-09T10:52:38+02:00"}

reinstalling qemu and lima didnt bring the file back, so I gave up and brew removed colima, and rm -rf .colima folder.

I hope somebody can post a fix, my containers are huge and it wastes a lot of time to pull them again.

Versions
qemu-img --version
qemu-img version 8.2.0
Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers

limactl --version
limactl version 0.19.1

colima version
colima version 0.6.7
git commit: ba1be00
runtime: docker
arch: x86_64
client: v24.0.7
server: v24.0.7

denistorjai · 2024-01-15T17:13:17Z

I just managed to recreate this exact same issue by accident.

Starting Colima and then restarting your PC causes it to not be able to start. After running the stopping Colima command and starting again it runs as intended.

daveyarwood · 2024-01-16T16:17:03Z

I tried many of the things above and was still getting the same "connection refused" error from the OP.

What finally ended up working for me was:

brew uninstall colima qemu lima
rm -rf ~/.colima
brew install colima
brew services restart colima
colima restart

laacpleesis · 2024-01-18T16:13:13Z

Not a fan of the the hard reinstall approach. If there was a quickfix, so I dont need to recreate all the containers, it would be fine by me. I also notice, that it happens after shutting down my mac.

So replicating scenario could be something like
colima start
start some container
shutdown mac with colima and container running.
colima start -> error

I have 4 containers running, started with docker compose. tomcat, database, java etc.

riconeitzel · 2024-01-25T12:52:54Z

SOLUTION FOR ME WAS:

#938 (comment)

Remove the _networks folder and start colima!

HatemTemimi · 2024-02-16T09:00:32Z

@laacpleesis I tried a lot of solution including, purging config, new install with brew, and the only one that worked for me was: brew remove qemu lima colima && rm -rf ~/.lima && rm -rf ~/.colima which is the hard delete, I am on MacOS Sonoma 14.3.1

sergeybe2 · 2024-02-28T12:15:57Z

This command helped me:

rm ~/.colima/_lima/_networks/user-v2/usernet_user-v2.pid

Run it after colima stop -f

MikeJansenNextira · 2024-02-28T16:09:56Z

SOLUTION FOR ME WAS:

#938 (comment)

Remove the _networks folder and start colima!

That worked for me.

bradj · 2024-04-05T19:21:14Z

SOLUTION FOR ME WAS:

#938 (comment)

Remove the _networks folder and start colima!

Thank you.

spaceneedle2019 · 2024-06-10T09:51:57Z

This command helped me:
rm ~/.colima/_lima/_networks/user-v2/usernet_user-v2.pid
Run it after colima stop -f

This solution helped me out solving the problem. Thank you. :)

rpkoller mentioned this issue Oct 11, 2022

"colima stop -f" not working when startup status is unknown #439

Closed

3 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Colima unable to restart on m1 after operating system restart #381

Colima unable to restart on m1 after operating system restart #381

jamie-smyth-at-thistle commented Jul 29, 2022

abiosoft commented Jul 29, 2022

jamie-smyth-at-thistle commented Jul 29, 2022

dip-thistle commented Aug 1, 2022 •

edited

Loading

abiosoft commented Aug 1, 2022

Jsince99 commented Aug 23, 2022

abiosoft commented Aug 23, 2022

Jerome1337 commented Nov 21, 2022 •

edited

Loading

Agnibho-8 commented Jan 24, 2023

abiosoft commented Jan 24, 2023 via email •

edited

Loading

dehengxu commented Mar 29, 2023

davidkyles commented Apr 27, 2023

davepoon commented May 3, 2023

protometa commented Sep 26, 2023

joachim-n commented Oct 3, 2023

skgandikota commented Oct 22, 2023

drupalninja commented Dec 12, 2023

farooqkhanDH commented Jan 2, 2024

laacpleesis commented Jan 9, 2024 •

edited

Loading

denistorjai commented Jan 15, 2024

daveyarwood commented Jan 16, 2024

laacpleesis commented Jan 18, 2024 •

edited

Loading

riconeitzel commented Jan 25, 2024

HatemTemimi commented Feb 16, 2024 •

edited

Loading

sergeybe2 commented Feb 28, 2024

MikeJansenNextira commented Feb 28, 2024

bradj commented Apr 5, 2024

spaceneedle2019 commented Jun 10, 2024

Colima unable to restart on m1 after operating system restart #381

Colima unable to restart on m1 after operating system restart #381

Comments

jamie-smyth-at-thistle commented Jul 29, 2022

Description

Version

Operating System

Reproduction Steps

Expected behaviour

Additional context

abiosoft commented Jul 29, 2022

jamie-smyth-at-thistle commented Jul 29, 2022

dip-thistle commented Aug 1, 2022 • edited Loading

abiosoft commented Aug 1, 2022

Jsince99 commented Aug 23, 2022

abiosoft commented Aug 23, 2022

Jerome1337 commented Nov 21, 2022 • edited Loading

Agnibho-8 commented Jan 24, 2023

abiosoft commented Jan 24, 2023 via email • edited Loading

dehengxu commented Mar 29, 2023

davidkyles commented Apr 27, 2023

davepoon commented May 3, 2023

protometa commented Sep 26, 2023

joachim-n commented Oct 3, 2023

skgandikota commented Oct 22, 2023

drupalninja commented Dec 12, 2023

farooqkhanDH commented Jan 2, 2024

laacpleesis commented Jan 9, 2024 • edited Loading

denistorjai commented Jan 15, 2024

daveyarwood commented Jan 16, 2024

laacpleesis commented Jan 18, 2024 • edited Loading

riconeitzel commented Jan 25, 2024

HatemTemimi commented Feb 16, 2024 • edited Loading

sergeybe2 commented Feb 28, 2024

MikeJansenNextira commented Feb 28, 2024

bradj commented Apr 5, 2024

spaceneedle2019 commented Jun 10, 2024

dip-thistle commented Aug 1, 2022 •

edited

Loading

Jerome1337 commented Nov 21, 2022 •

edited

Loading

abiosoft commented Jan 24, 2023 via email •

edited

Loading

laacpleesis commented Jan 9, 2024 •

edited

Loading

laacpleesis commented Jan 18, 2024 •

edited

Loading

HatemTemimi commented Feb 16, 2024 •

edited

Loading