Help Center/
Cloud Container Engine/
User Guide (Kuala Lumpur Region)/
Clusters/
Upgrading a Cluster/
Troubleshooting for Pre-upgrade Check Exceptions/
Number of Node Images
Updated on 2025-12-08 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.
You can run the command below to delete an image with the <none> tag. Such images are typically left from builds or updates.
- For nodes that use Docker
docker image prune
- For nodes that use containerd
- View all images with the none tags.
crictl images | grep "<none>"
- Delete all images with the none tags 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
- View all images with the none tags.
- For nodes that use Docker
- 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.
Parent topic: Troubleshooting for Pre-upgrade Check Exceptions
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot