yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
218900ecfc237f6c0ba9f9684f9afa10f1d5ea9a
doc-exports/docs/cce/umn/cce_10_0518.html
qiujiandong1 ab1e53a279 CCE UMN 20251031 version 
Reviewed-by: Gergo-Bence Lorincz <a200452876@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
2026-01-15 10:25:22 +00:00

2.3 KiB
Raw Blame History

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.

Solutions

  • 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
      1. Check all dangling images.
        crictl images | grep "<none>"
      2. 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
  • 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.