launchd auto start support missing?
Open
enhancement
- Dominant language
- Go
- Stars
- 30.8k
- Forks
- 613
- PR merge metrics
- No merged PRs in 30d
Description
The colima stuff is working great as a Docker Desktop replacement with one minor exception for me. I've been unable to get it to autostart via launchd. I *think* that it is likely because the "start" command forks the hypervisor and then eventually exits. My understanding is that launchd expects the command to run indefinitely. I took a look at the code, but not conversant enough in Go to figure out how to "fix" this. Is this something that is on the roadmap?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.