colima
colima copied to clipboard
Error retrieving current runtime: empty value
Description
Every time I create a VM, it works. When I reboot the machine, it does not work. Here is what I did:
## Cleanup
server@server-buildserver-4 ~ % rm -rf .lima .colima
## Creation
server@server-buildserver-4 ~ % colima start --cpu 8 --memory 6 --disk 128 --vm-type=vz --vz-rosetta
INFO[0000] starting colima
INFO[0000] runtime: docker
INFO[0001] creating and starting ... context=vm
INFO[0012] provisioning ... context=docker
INFO[0013] starting ... context=docker
INFO[0014] done
server@server-buildserver-4 ~ % 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/server/.colima/default/docker.sock
server@server-buildserver-4 ~ % docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
## Reboot
server@server-buildserver-4 ~ % sudo reboot
## After reboot
server@server-buildserver-4 ~ % colima status
FATA[0000] error retrieving current runtime: empty value
server@server-buildserver-4 ~ % colima ls
PROFILE STATUS ARCH CPUS MEMORY DISK RUNTIME ADDRESS
default Running aarch64 8 6GiB 128GiB docker
server@server-buildserver-4 ~ % colima ssh
FATA[0000] exit status 255
Version
colima version 0.7.5 git commit: 1588c066b9ab9dae8205ef265929c7eb43dca473 limactl version 0.23.2 qemu-img version 9.1.1 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)
- [X] Apple Silicon >= 14 (Sonoma)
- [ ] Linux
Output of colima status
FATA[0000] error retrieving current runtime: empty value
Reproduction Steps
See description.
Expected behaviour
colima status just works.
Additional context
Mac Mini M1 (256 GiB SSD and 8 GiB memory), running headless. I access it via SSH.
Colima is automatically started using brew services start colima.
I tried to reinstall Colima, but that does not make a difference.
same here. I don't even need to reboot. After every my lid close-open cycle I have unresponsive colima with same behaviour:
~ [1]> colima status
FATA[0000] error retrieving current runtime: empty value
~ [1]> colima ls
PROFILE STATUS ARCH CPUS MEMORY DISK RUNTIME ADDRESS
default Running aarch64 4 8GiB 100GiB docker
~> colima ssh
ssh: connect to host 127.0.0.1 port 61514: Connection refused
FATA[0000] exit status 255