You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to push a local image to a remote repository, but I keep encountering the error content digest xxx: not found. The container created from this image is running without issues! Doesn't a running container require all the image layers to be present locally?
When I use the pull command to re-download the image, I can push it without any problems, but this isn't the solution I want. Can I configure Kubernetes to ensure the image is fully downloaded before starting the container? Could this be related to some specific settings?
By the way, the host architecture is linux/arm64, and the image is also linux/arm64, not multi-platform. I tried running a similar container on linux/amd64, and the image was complete.
$ ctr --version
ctr github.com/containerd/containerd v1.6.8
$ ctr -n k8s.io container ls | grep ide
fd551dd81f1f881fe6e922a258727e9544d5ec6d0b56c163e3b1041d6d6b57d5 registry.io/public/mindformers1.0-mindspore2.2.11-ide:latest io.containerd.runtime.v1.linux
$ crictl ps | grep ide
fd551dd81f1f8 ba7db6c0865f3 31 minutes ago Running ide 0 e093e135ddbb7 pod-1249413021557993472
$ ctr -n k8s.io image check | grep ide
registry.io/public/mindformers1.0-mindspore2.2.11-ide:latest application/vnd.docker.distribution.manifest.v2+json sha256:7c079f49499b7292388916d53a29cba5af71b0618b7bb87cf6ba802dee026d6e incomplete (11/17) 391.5 MiB/5.2 GiB true
registry.io/public/mindformers1.0-mindspore2.2.11-ide@sha256:4d557be7f18c87d05dec704e741a3c0afc251c164b03fa722203c47caed3b2e4 application/vnd.docker.distribution.manifest.list.v2+json sha256:4d557be7f18c87d05dec704e741a3c0afc251c164b03fa722203c47caed3b2e4 incomplete (11/17) 391.5 MiB/5.2 GiB true
$ ctr -n k8s.io image push registry.io/public/mindformers1.0-mindspore2.2.11-ide:latest
manifest-sha256:7c079f49499b7292388916d53a29cba5af71b0618b7bb87cf6ba802dee026d6e: waiting |--------------------------------------|
elapsed: 0.1 s total: 0.0 B (0.0 B/s)
ctr: content digest sha256:6cba4020c0a193cd551ed8edf368670967e3546345b52c4ec66cb0931436e9b9: not found
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm trying to push a local image to a remote repository, but I keep encountering the error content digest xxx: not found. The container created from this image is running without issues! Doesn't a running container require all the image layers to be present locally?
When I use the pull command to re-download the image, I can push it without any problems, but this isn't the solution I want. Can I configure Kubernetes to ensure the image is fully downloaded before starting the container? Could this be related to some specific settings?
By the way, the host architecture is linux/arm64, and the image is also linux/arm64, not multi-platform. I tried running a similar container on linux/amd64, and the image was complete.
Beta Was this translation helpful? Give feedback.
All reactions