1 Answer
- Newest
- Most votes
- Most comments
0
Because containerd cannot obtain the ECR credentials to pull the sandbox container image. You can run
systemctl restart sandbox-image
to trigger the pull, but you still need to investigate why the image was removed. For example, possible reasons:
- Use a custom script that runs on each node to clean up unused images on the node and exit the container, this will also delete the pause image on the node. The script can be modified to exclude some images on the node.
- Use a command like crictl rmi --prune to manually delete the image. Avoid similar operations and leave it to kubelet for image recycling.
The kubelet will perform garbage collection on unused images every two minutes and garbage collection on unused containers every minute. You should avoid using external garbage collection tools, as external tools may break the kubelet's behavior and remove containers that should be retained.
Relevant content
asked 2 years ago
- AWS OFFICIALUpdated 10 months ago
