colima icon indicating copy to clipboard operation
colima copied to clipboard

Colima seems to "die" after sleep on Mac.

Open emilpriver opened this issue 1 year ago • 7 comments

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

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

Reproduction Steps

1.Put computer to a "hard" sleep 2. See if Colima is stoped by for example running docker ps 3. Start Colima with colima stop && colima start.

Expected behaviour

To still be running.

Additional context

No response

emilpriver avatar Oct 31 '22 08:10 emilpriver

+1

karlhaworth avatar Jan 05 '23 19:01 karlhaworth

+1

kamiltrantvananh avatar Jan 06 '23 09:01 kamiltrantvananh

+1

andreyors avatar May 02 '23 06:05 andreyors

It also seems to sometimes hang when executing colima stop, just printing INFO[0000] stopping colima for ages

dzeglen-evo avatar May 02 '23 08:05 dzeglen-evo

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.

dikderoy avatar Sep 06 '23 13:09 dikderoy

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.

winterqt avatar Oct 14 '23 02:10 winterqt

Just experienced same behavior on an intel mac

smazurov avatar Feb 23 '24 22:02 smazurov