abiosoft / abiosoft/colima

Stuck at FATA[0600] error starting vm: error at 'starting': exit status 1

Open
#527 1 comment 11 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
30.8k
Forks
613
PR merge metrics
No merged PRs in 30d

Description

### Description

cannot start colima after some time it is stuck at
FATA[0600] error starting vm: error at 'starting': exit status 1

`INFO[0000] starting colima
INFO[0000] runtime: docker
INFO[0000] creating and starting ... context=vm
> Terminal is not available, proceeding without opening an editor
> "Attempting to download the image from \"https://github.com/abiosoft/alpine-lima/releases/download/colima-v0.5.0-2/alpine-lima-clm-3.16.2-aarch64.iso\"" digest="sha512:06abfa8c9fd954f8bfe4ce226bf282dd06e9dfbcd09f57566bf6c20809beb5a3367415b515e0a65d6a1638ecfd3a3bb3fb6d654dee3d72164bd0279370448507"
> Using cache "/Users/adm/Library/Caches/lima/download/by-url-sha256/c37acb6308026b2fe12f6c0ef3371f690b3e33ee6b5d37d5dc68684f8fd5ee52/data"
> [hostagent] Starting VZ (hint: to watch the boot progress, see "/Users/adm/.lima/colima/serial.log")
> [hostagent] Setting up Rosetta share
> SSH Local Port: 49888
> [hostagent] new connection from to
> [hostagent] [VZ] - vm state change: running
> [hostagent] Waiting for the essential requirement 1 of 3: "ssh"
> [hostagent] 2022/12/20 17:48:12 tcpproxy: for incoming conn 127.0.0.1:49891, error dialing "192.168.5.15:22": connect tcp 192.168.5.15:22: no route
> [hostagent] Waiting for the essential requirement 1 of 3: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 3: "ssh"`

### Version

Colima Version:0.5.0
Lima Version:0.14.1
Qemu Version:7.2.0

### Operating System

- [ ] macOS Intel
- [X] macOS M1
- [ ] Linux

### Reproduction Steps

1.colima start
2.
3.

### Expected behaviour

_No response_

### Additional context

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue is about Colima failing to start a VM on macOS M1, with logs showing a network connectivity error ('no route'). Start by examining the Lima hostagent logs at ~/.lima/colima/serial.log and the Colima source code around VM startup and network configuration. Look for recent changes in the Lima dependency or network setup. Testing involves reproducing the issue on an M1 Mac and debugging the network route establishment.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go, macos
Domain
cli, devops, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.