How do I debug pod error `"failed to receive. \"waiting for init ready\". BrokenChannel"` in k3s?

[Jiaxiao Zhou]

We've observed a recurring error in pod logs that states:

"Error: failed to create containerd task: failed to create shim task: Others("failed to receive. "waiting for init ready". BrokenChannel"): unknown"

This issue is known to be linked to specific problems (e.g., Issue #173). To effectively assist in debugging, we require detailed Containerd logs from affected users.

This issue serves as a guide for users on how to access and provide Containerd logs from k3s clusters.

Steps to Access Containerd Logs

Refer to k3s Documentation: The k3s logs FAQ provides general guidance on locating various logs within k3s.

Accessing Containerd Logs:

• Utilize docker exec to enter your workload container.
• Once inside, navigate to /var/lib/rancher/k3s/agent/containerd/containerd.log. This file contains the Containerd logs.
• You might encounter log entries similar to ">>> running spin trigger".

Reporting

After locating the Containerd logs, please create a new issue and attach the relevant log excerpts. This will greatly assist in diagnosing and addressing the root cause of the error you're encountering.