OS reboot almost always breaks Colima

[junglebells]

Description

Looking for best practices for restarting host machine. Using Apple Silicon M2 Sequoia. Installed "brew install colima" and "brew services start colima" and "brew install docker docker-compose"

Here are the scenarios:

1. If I reboot machine with docker containers still running - Colima almost always comes back in "broken" status
2. If I reboot after shutting down all containers - it most likely comes back in running state.
3. If I define an alias in ~/.zshrc file, scenario 1 above is pretty much certain, however with no ~/.zshrc file present, chances of coming back in running state are high
4. If I stop Colima before reboot, it most likely comes back in "running" state

What is the best practice to reboot host? Recovering from "broken" state by deleting and recreating is not a viable option. Please advise.

Version

colima version 0.7.5
git commit: 1588c06
limactl version 0.23.2
qemu-img version 9.1.0
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers

Operating System

• macOS Intel <= 13 (Ventura)
• macOS Intel >= 14 (Sonoma)
• Apple Silicon <= 13 (Ventura)
• Apple Silicon >= 14 (Sonoma)
• Linux

Output of 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] socket: unix:///Users/mini/.colima/default/docker.sock

Reproduction Steps

see description

Expected behaviour

rebooting host machine brings back colima and running containers properly (as it does in docker on linux environments)

Additional context

does populating ~/.zshrc have anything to do with it? I'd like to define some alias in this file.