abiosoft/colima · error
'colima model' requires krunkit VM type for GPU access, curr
Error message
'colima model' requires krunkit VM type for GPU access, current VM type is %s Start colima with: colima start --runtime docker --vm-type krunkit
What it means
GPU access for AI models is only wired up for the krunkit VM type; the loaded instance config reported a different VMType (vz, qemu, ...). VM type is fixed when the VM is created/started, so the only remedy is restarting with the command embedded in the message.
Source
Thrown at model/runner.go:106
}
// check runtime is docker
r, err := a.Runtime()
if err != nil {
return err
}
if r != docker.Name {
return fmt.Errorf("'colima model' requires docker runtime, current runtime is %s\n"+
"Start colima with: colima start --runtime docker --vm-type krunkit", r)
}
// check VM type is krunkit (required for GPU access)
conf, err := configmanager.LoadInstance()
if err != nil {
return fmt.Errorf("error loading instance config: %w", err)
}
if conf.VMType != limaconfig.Krunkit {
return fmt.Errorf("'colima model' requires krunkit VM type for GPU access, current VM type is %s\n"+
"Start colima with: colima start --runtime docker --vm-type krunkit", conf.VMType)
}
// check krunkit binary exists on host
if err := util.AssertKrunkit(); err != nil {
return err
}
return nil
}
// dockerRunner implements Runner for Docker Model Runner.
type dockerRunner struct{}
func (d *dockerRunner) Name() RunnerType {
return RunnerDocker
}
View on GitHub (pinned to c3a5f9184d)
Solutions
- Restart as instructed: colima stop && colima start --runtime docker --vm-type krunkit — also make sure the krunkit binary is present, the very next check (util.AssertKrunkit) enforces it
- Verify with colima status that the VM type took effect
- If krunkit is unavailable on your platform, model commands cannot be used on that machine
Defensive patterns
Strategy: validation
Validate before calling
// surface the requirement before user-visible work begins
conf, err := configmanager.LoadInstance()
if err == nil && conf.VMType != limaconfig.Krunkit {
return fmt.Errorf("restart required: colima start --runtime docker --vm-type krunkit")
} Prevention
- Create model-oriented profiles with --runtime docker --vm-type krunkit from day one
- Install and verify krunkit before enabling model workflows
When it happens
Trigger: A default colima start (vz on macOS, qemu elsewhere) or an explicit --vm-type vz/qemu profile, followed by any colima model command.
Common situations: Long-lived profiles created before model support existed; users unaware that model GPU passthrough requires krunkit.
Related errors
- 'colima model' requires docker runtime, current runtime is %
- error loading instance config: %w
- invalid downloader %q: must be one of %s, %s
- dependency check failed for VM: %w
- error retrieving current runtime: empty value
AI-assisted analysis of abiosoft/colima@c3a5f9184d (2026-08-15).
Data as JSON: /api/errors/e86059997f1e3913.
Report an issue: GitHub.