colima: k3s.service failed because the control process exited with error code

Description

I’m getting a k3s.service failure when running colima start.

colima start -k --network-address
INFO[0000] starting colima
INFO[0000] runtime: docker+k3s
INFO[0000] preparing network ...                         context=vm
INFO[0001] creating and starting ...                     context=vm
INFO[0016] provisioning ...                              context=docker
INFO[0017] starting ...                                  context=docker
INFO[0033] provisioning ...                              context=kubernetes
INFO[0034] downloading and installing ...                context=kubernetes
INFO[0039] loading oci images ...                        context=kubernetes
INFO[0045] starting ...                                  context=kubernetes
> Warning: The unit file, source configuration file or drop-ins of k3s.service changed on disk. Run 'systemctl daemon-reload' to reload units.
> Job for k3s.service failed because the control process exited with error code.
> See "systemctl status k3s.service" and "journalctl -xeu k3s.service" for details.
FATA[0046] error starting kubernetes: exit status 1

Version

colima version && limactl --version && qemu-img --version
colima version 0.7.1
git commit: ce7b155dbeb7843ac0d9966a6ad19dc8e3b56bb8
limactl version 0.22.0
qemu-img version 9.0.2
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers

Operating System

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

Output of colima status

colima status
FATA[0000] error retrieving current runtime: empty value

Reproduction Steps

  1. Start up macOS
  2. Run colima start -k --network-address

Expected behaviour

colima should start without k3s.service error.

Should start kubernetes without exit code.

Additional context

This was working previously (last week before mac restart) and had installed from HEAD.

I had docker desktop installed previously, but have since uninstalled it.

I have deleted clusters and started again from scratch. Have uninstalled colima and reinstalled (now on version 0.7.1). Same error.

This could be on my end, but I can’t find anything online that helps.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 18 (8 by maintainers)

Most upvoted comments

OK, to hopefully help someone else out, we use MDM for our laptops and our IT has reported that the Enable stealth mode setting was causing issues for colima.

This is all working for me now, but I will try to add more details if it comes up again. Cheers