Description
Hi All,
Recently we have upgraded our eks cluster from 1.23 to 1.24, where docker container runtime is removed and containerd container runtime is running, post this upgraded activity we have observed that pods are failing with below error, especially with bigger images ~4000MB size, so we have followed the solution given in #4604 (comment) , however still no luck, could some please assist on this
Note: iops and throughput are with in limit and we dont see any spike
error
Error: failed to reserve container name
Steps to reproduce the issue
Describe the results you received and expected
Out put received
Events:
Type Reason Age From Message
Normal Scheduled 4m16s default-scheduler Successfully assigned to xxxxxxx
Warning Failed 2m15s kubelet Error: context deadline exceeded
Warning Failed 56s (x7 over 2m15s) kubelet Error: failed to reserve container name "example-database-pod-7c8966b6dhjbd8_v7_401407e8-12f2-41d5-95f3-487293d9e66f_0": name "example-database-pod_xxxx-v7-navitus-rxf-9287-example-database-pod-7c8966b6dhjbd8_v7_401407e8-12f2-41d5-95f3-487293d9e66f_0" is reserved for "c03c3f65ec9d800fc2a1595603cc09af42662d85f32265871ef3459a86dd4954"
expected result
Pod should come in to running state
What version of containerd are you using?
containerd://1.6.19
Any other relevant information
No response
Show configuration if it is related to CRI plugin.
No response
Description
Hi All,
Recently we have upgraded our eks cluster from 1.23 to 1.24, where docker container runtime is removed and containerd container runtime is running, post this upgraded activity we have observed that pods are failing with below error, especially with bigger images ~4000MB size, so we have followed the solution given in #4604 (comment) , however still no luck, could some please assist on this
Note: iops and throughput are with in limit and we dont see any spike
error
Error: failed to reserve container name
Steps to reproduce the issue
Describe the results you received and expected
Out put received
Events:
Type Reason Age From Message
Normal Scheduled 4m16s default-scheduler Successfully assigned to xxxxxxx
Warning Failed 2m15s kubelet Error: context deadline exceeded
Warning Failed 56s (x7 over 2m15s) kubelet Error: failed to reserve container name "example-database-pod-7c8966b6dhjbd8_v7_401407e8-12f2-41d5-95f3-487293d9e66f_0": name "example-database-pod_xxxx-v7-navitus-rxf-9287-example-database-pod-7c8966b6dhjbd8_v7_401407e8-12f2-41d5-95f3-487293d9e66f_0" is reserved for "c03c3f65ec9d800fc2a1595603cc09af42662d85f32265871ef3459a86dd4954"
expected result
Pod should come in to running state
What version of containerd are you using?
containerd://1.6.19
Any other relevant information
No response
Show configuration if it is related to CRI plugin.
No response