Unable to start colima when host is not connected to any network

[mduran80]

Description

Colima (or lima) is unable to start the VM when the host is offline, disconnected from wired or wireless networks. It fails the first time it is launched under these conditions and then hangs the rest of the times it is attempted to be restarted.

These are the logs of those attempts plus logs of ha.stderr.log

➜  .docker colima stop --force
INFO[0000] stopping colima
INFO[0000] stopping ...                                  context=vm
INFO[0000] done

➜  .docker colima start --very-verbose
TRAC[0000] cmd ["limactl" "info"]
TRAC[0000] cmd ["system_profiler" "-json" "SPHardwareDataType"]
TRAC[0000] cmd ["limactl" "list" "colima" "--json"]
INFO[0000] starting colima
INFO[0000] runtime: docker
TRAC[0000] cmd ["limactl" "list" "colima" "--json"]
TRAC[0000] cmd ["/opt/homebrew/bin/colima" "daemon" "status" "default"]
TRAC[0000] cmd ["/opt/homebrew/bin/colima" "daemon" "start" "default" "--inotify" "--inotify-runtime" "docker" "--inotify-dir" "/Users/user/" "--inotify-dir" "/tmp/colima/" "--very-verbose"]
TRAC[0000] cmd ["/opt/homebrew/bin/colima" "daemon" "status" "default"]
TRAC[0001] cmd ["/opt/homebrew/bin/colima" "daemon" "status" "default"]
TRAC[0001] cmd ["system_profiler" "-json" "SPHardwareDataType"]
INFO[0001] starting ...                                  context=vm
TRAC[0001] cmd ["limactl" "start" "colima"]
> Using the existing instance "colima"
> Starting the instance "colima" with VM driver "vz"
> vmType vz: ignoring networks[0]: [Metric]
> [hostagent] hostagent socket created at /Users/user/.colima/_lima/colima/ha.sock
> [hostagent] Starting VZ (hint: to watch the boot progress, see "/Users/user/.colima/_lima/colima/serial*.log")
> exiting, status={Running:false Degraded:false Exiting:true Errors:[] SSHLocalPort:0} (hint: see "/Users/user/.colima/_lima/colima/ha.stderr.log")
FATA[0002] error starting vm: error at 'starting': exit status 1

➜  .docker colima start --very-verbose
TRAC[0000] cmd ["limactl" "info"]
TRAC[0000] cmd ["system_profiler" "-json" "SPHardwareDataType"]
TRAC[0000] cmd ["limactl" "list" "colima" "--json"]
INFO[0000] starting colima
INFO[0000] runtime: docker
TRAC[0000] cmd ["limactl" "list" "colima" "--json"]
TRAC[0000] cmd ["/opt/homebrew/bin/colima" "daemon" "status" "default"]
TRAC[0000] cmd ["/opt/homebrew/bin/colima" "daemon" "stop" "default"]
TRAC[0000] cmd ["/opt/homebrew/bin/colima" "daemon" "start" "default" "--inotify" "--inotify-runtime" "docker" "--inotify-dir" "/Users/user/" "--inotify-dir" "/tmp/colima/" "--very-verbose"]
TRAC[0000] cmd ["/opt/homebrew/bin/colima" "daemon" "status" "default"]
TRAC[0001] cmd ["/opt/homebrew/bin/colima" "daemon" "status" "default"]
TRAC[0001] cmd ["system_profiler" "-json" "SPHardwareDataType"]
INFO[0001] starting ...                                  context=vm
TRAC[0001] cmd ["limactl" "start" "colima"]
> Using the existing instance "colima"

ha.stderr.log:

➜  ~ tail .colima/_lima/colima/ha.stderr.log
{"level":"debug","msg":"Creating iso file /Users/user/.colima/_lima/colima/cidata.iso","time":"2024-12-12T20:29:02+01:00"}
{"level":"debug","msg":"Using /var/folders/1v/3tlt5gzs0q7gjwdhv3lflzh80000gn/T/diskfs_iso3250094531 as workspace","time":"2024-12-12T20:29:02+01:00"}
{"level":"debug","msg":"Failed to detect CPU features. Assuming that AES acceleration is available on this Apple silicon.","time":"2024-12-12T20:29:02+01:00"}
{"level":"debug","msg":"OpenSSH version 9.8.1 detected","time":"2024-12-12T20:29:02+01:00"}
{"level":"debug","msg":"AES accelerator seems available, prioritizing aes128-gcm@openssh.com and aes256-gcm@openssh.com","time":"2024-12-12T20:29:02+01:00"}
{"level":"info","msg":"hostagent socket created at /Users/user/.colima/_lima/colima/ha.sock","time":"2024-12-12T20:29:02+01:00"}
{"level":"info","msg":"Starting VZ (hint: to watch the boot progress, see \"/Users/user/.colima/_lima/colima/serial*.log\")","time":"2024-12-12T20:29:02+01:00"}
{"level":"debug","msg":"Kernel file \"/Users/user/.colima/_lima/colima/kernel\" not found","time":"2024-12-12T20:29:02+01:00"}
{"level":"debug","msg":"Using EFI Boot Loader","time":"2024-12-12T20:29:02+01:00"}
{"level":"fatal","msg":"dial unix /Users/user/.colima/_lima/_networks/user-v2/user-v2_fd.sock: connect: no such file or directory","time":"2024-12-12T20:29:02+01:00"}

Version

0.8.0

Operating System

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

Output of colima status

➜  .docker colima status -e
FATA[0000] colima is not running

Reproduction Steps

1. Run colima stop --force
2. Disconnect all networks
3. Run colima start --very-verbose

Expected behaviour

Start colima normally in offline environments

Additional context

No response

[abiosoft]

This should be resolved with the latest release https://github.com/abiosoft/colima/releases/tag/v0.8.1.

[lfdebrux]

I'm seeing a similar issue to this on colima v0.8.1, where if I'm not connected to a network colima start hangs indefinitely.

Additionally I've noticed that there are no logs in the ha.stderr.log file, but there is something in the log file for the network in ~/.colima/_lima/_networks/user-v2/usernet.user-v2.stderr.log:

time="2025-01-14T08:41:15Z" level=fatal msg="cannot add network services: no DNS servers configured in /etc/resolv.conf"

I was able to workaround by adding nameserver 8.8.8.8 to /etc/resolv.conf.

[AnthoBalitrand]

Hello,
This is probably linked to this issue : lima-vm/lima#3050