Open emilpriver opened 1 year ago
+1
+1
+1
It also seems to sometimes hang when executing colima stop
, just printing INFO[0000] stopping colima
for ages
same on M2 processors
also very weirdly, sometimes it is "not entirely" dead.
i.e. it's being stuck launching the containers. but docker (over mounted socket) reports that networks and container were Created
, but they do not proceed to Running
state.
while docker commands continue to report state.
ie. I can do docker images
or docker ps
and they respond just fine. I can also download new images, but containers won't start.
I can reproduce this, but colima stop --force
at least lets colima start
work again. It doesn't seem like the force stop leaves any processes dangling.
Just experienced same behavior on an intel mac
Description
If I leave my computer and my computer sleeps for a longer time, for example over night do my Colima stop and I need to call run
colima stop && colima start
in order to start it again. It's not a big problem haha, more a nice thing to be able to skip.Version
Colima Version: colima version 0.4.6 Lima Version: limactl version 0.12.0 Qemu Version: qemu-img version 7.1.0
Operating System
Reproduction Steps
1.Put computer to a "hard" sleep
docker ps
colima stop && colima start
.Expected behaviour
To still be running.
Additional context
No response