Help Center/ Cloud Container Engine/ User Guide/ Clusters/ Upgrading a Cluster/ Troubleshooting for Pre-upgrade Check Exceptions/ Number of Node Images
Updated on 2025-09-15 GMT+08:00
Number of Node Images
Check Items
Check the number of images on your node. If there are more than 1000 images, it takes a long time for Docker to start, affecting the standard Docker output and functions such as Nginx.
Solution
- If there are too many images on a node, you can delete unnecessary images from the node. Delete dangling (<none>) images. Such images are typically left from builds or updates.
- For Docker nodes
docker image prune
- For containerd nodes
- Check all dangling images.
crictl images | grep "<none>"
- Delete all dangling images in batches. Use awk to extract the image IDs and pipe them to xargs for deletion.
crictl images | grep "<none>" | awk '{print $3}' | xargs -r crictl rmi
- Check all dangling images.
- For Docker nodes
- Too many images slow Docker or containerd startup on your nodes. This delays containers that burst stdout logs for just a few seconds typically. Skip this check if services are not affected.
What is your overall rating for this page?
0
1
2
3
4
5
6
7
8
9
10
Very dissatisfiedVery satisfied
Thank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.