common errors

k3s not starting

Dec 18 23:17:26 wingzero k3s[240059]: time="2023-12-18T23:17:26Z" level=error msg="containerd exited: exit status 1"
Dec 18 23:17:26 wingzero systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Dec 18 23:17:26 wingzero systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
Dec 18 23:17:26 wingzero systemd[1]: Failed to start Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 14232 and the job result is failed.
Dec 18 23:17:26 wingzero systemd[1]: k3s.service: Consumed 3.087s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit k3s.service completed and consumed the indicated resources.

Solution Ensure no ports required by k3s are being used e.g. in sudo cat /var/lib/rancher/k3s/agent/containerd/containerd.log

time="2023-12-19T00:02:06.245887868Z" level=fatal msg="Failed to run CRI service" error="stream server error: listen tcp 127.0.0.1:10010: bind: address already in use"