- Newest
- Most votes
- Most comments
Hello.
Troubleshooting Steps:
Check Kernel Version Compatibility:
Identify the kernel version of your EKS cluster nodes. You can usually find this with uname -r on an SSH session to the node. Consult the documentation for the container image you're using to ensure compatibility with the EKS cluster kernel version.
Investigate Container Runtime Logs:
Look for relevant entries in the container runtime logs (e.g., containerd or Docker logs) that might shed light on the cgroup configuration issue. This might involve using commands like journalctl or the specific container runtime logging mechanism.
Review Container Image:
If a kernel version mismatch seems unlikely, consider examining the container image itself. You can use a tool like docker inspect to view the image configuration and identify any cgroup-related settings that might be causing conflicts.
Update EKS Cluster (if applicable):
If the issue is related to a known kernel limitation, consider updating your EKS cluster to a newer version with a more recent kernel that might have the required cgroup features.
Additional Follow below links
Similar issue on GitHub (regarding cgroup and procHooks):
https://github.com/containerd/containerd/issues/8139
Docker documentation on cgroups:
Relevant content
asked 2 years ago
asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
