launchd auto start support missing?

[csetera]

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?

[abiosoft]

Yeah, auto-startup has not been added to the project.

[csetera]

Thanks. In the short term, simply making an option that leaves the colima application running in the foreground might be enough to give people a way to wrap it up in launchd. Anyway... Thanks for this project!

[Amar1729]

see also #96

[lloeki]

Also related:

• Colima daemon #262
• Daemon fail in when launching colima start from launchd user agent #490