-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Containerd Image pull fails intermittently with EOF error for Harbor private registry #8971
Comments
I think it might be related to your registry. Would you mind to use debug mode to rerun it again? thanks |
|
@charugarg2810 I think there is some wrong with this blob. Would you mind to use |
The thing is it's an intermittent issue and is happening for multiple images. On some retries (~ 10-15 times) it gets auto-resolved. |
Below is the debug output for some different image: |
So, I think it maybe related to your registry. :( |
The only concern is it's working fine with Docker. Only Conatinerd is failing. |
Maybe try containerd v1.6.23 https://github.com/containerd/containerd/tree/v1.6.23 and see if the issue still exists. Context: we got EOF errors before (not sure if it's the same root cause), and made a fix #8800 which should be included in 1.6.23. |
I tried but with no success.
|
Hi. I have the same issue with EKS 1.25 and containerd version 1.6.19 |
@d4n13lbc you too using the Harbor Docker registry? |
@charugarg2810 |
We have the same issue eith eks 1.25. |
Fatal error... New versions of kubernetes use crictl only, but crictl is not able to pull images by https. While this issue is not resolved, the single solution i had found is to switch harbor to work through http and force containerd do the same. |
We are seeing the same intermittent issue with JFrog Artifactory. |
Might this be a regression in What's the situation for everyone else who have chimed in on this issue? EDIT: For what it's worth it looks like there is an integration test checking for this error. |
Hit the same issue with containerd 1.7.11 with AWS ECR See
|
This issue is stale because it has been open 90 days with no activity. This issue will be closed in 7 days unless new comments are made or the stale label is removed. |
Not stale. |
The same error is reported, distribution v2.8.3 is used as a cache pull warehouse, and the node uses containerd 1.6.23. I strongly suspect that there is a problem with distribution, but the info/debug logs of the service are all Get HTTP requests, filesystem.getcontent,filesystem.Reader, filesystem.putcontent, response completed, filesystem.Delete repeatedly,no error log output |
I noticed the same issue in our build system, the root cause was that we messed up with docker cache and loaded (docker load) wrong images to build main app. |
This issue is stale because it has been open 90 days with no activity. This issue will be closed in 7 days unless new comments are made or the stale label is removed. |
This issue was closed because it has been stalled for 7 days with no activity. |
Description
Hi Team,
We have recently upgraded our EKS cluster from v1.23 to 1.24, which replaces the Docker with Containerd. Now in 1.24 clusters, we are seeing imagepullbackoff issues for harbor images. While trying to pull the image manually it gives below output.
Steps to reproduce the issue
Describe the results you received and expected
ctr -n k8s.io image pull harbor.registry.dns/image/path:1234 --user user1
Password:
harbor.registry.dns: resolved |++++++++++++++++++++++++++++++++++++++|
index-sha256:371b1e63285f74ff6927becf34a47f302e954c7835987c0660c63b8ac5bb4651: waiting |--------------------------------------|
manifest-sha256:1ec1ffc82b90a3e9cb7445c2079cb60a954b41303b0ac9174144ded2f4cccc05: done |++++++++++++++++++++++++++++++++++++++|
config-sha256:d437a0ad48fceb1463e1c2af0b35959ab5cbab3a4961009d1e964571d7d9e161: done |++++++++++++++++++++++++++++++++++++++|
layer-sha256:f868ac632a6f7994c589ce631afb99014698a783e173144bf4740e318303e992: downloading |++++++++++++++++++++++++++++++++------| 214.0 Mi/250.5 MiB
layer-sha256:7764d651778cbda3c7f069f86ba147bed458dd009da9fa8adea5b10fdce6b7fd: exists |++++++++++++++++++++++++++++++++++++++|
layer-sha256:b042aaf118281415531e49b79872d7acaccc799fc45c155968386191d5b0fe96: exists |++++++++++++++++++++++++++++++++++++++|
layer-sha256:d1978f9b30d3ea4c690f3b1d639eb3040c3d56a1dbf89363fa977585f7c202ea: exists |++++++++++++++++++++++++++++++++++++++|
layer-sha256:0b172db2480d88fcc4bec429da2777b56687dbcd82d80c19dc41e16ffc56d14b: done |++++++++++++++++++++++++++++++++++++++|
layer-sha256:f4ca923fee1c63e06eb59c3c36ee6d9f2c5109c36f65faa6ef1438665af7d2c8: exists |++++++++++++++++++++++++++++++++++++++|
layer-sha256:6fb9d4937c2de8d137362d704c8f8de084db756c885c5474d20dd69044024998: exists |++++++++++++++++++++++++++++++++++++++|
layer-sha256:76bf1f85fdf38a127d6047c9b3d96651797e2cb5825172dee23cb611f3111f9c: done |++++++++++++++++++++++++++++++++++++++|
layer-sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1: exists |++++++++++++++++++++++++++++++++++++++|
layer-sha256:fd3f1f3d715a631eef5b404d02efd10954d94660c657ac72fda312281b4f42bb: exists |++++++++++++++++++++++++++++++++++++++|
layer-sha256:fe906bbc5faed6202ead1ec035b9467f3cf02bf5120145dec708061c5e81c119: done |++++++++++++++++++++++++++++++++++++++|
layer-sha256:39182aedab0a7dad5dbd70262fbc13e54f2b2cab4f278078650936c2e7dae52a: done |++++++++++++++++++++++++++++++++++++++|
layer-sha256:381187300573beeff328abb31687c357112e575c9ca02b256683f98224cc7e93: done |++++++++++++++++++++++++++++++++++++++|
layer-sha256:6c9601c677052f34717209df96af5cb97a65f46af42afa86f69c946af48e0348: exists |++++++++++++++++++++++++++++++++++++++|
layer-sha256:373b6cb05c932efa90c2860309fbd932885aa1fe2d0b2d399d5aab81f2262c5a: exists |++++++++++++++++++++++++++++++++++++++|
layer-sha256:52c3e4aa8e82ec89a0cedcea37e8d9b4541b00d560d85874cb271fb80288e75b: done |++++++++++++++++++++++++++++++++++++++|
layer-sha256:2c594df67f226b623622ccac83bf2cea5024eab532cf930fc6f888011906a1fa: exists |++++++++++++++++++++++++++++++++++++++|
layer-sha256:e25e5e21d0a6a269d82a220ce0848c2862694dbee4956386a06f5e71ad8f892c: done |++++++++++++++++++++++++++++++++++++++|
layer-sha256:16c640aa63795ffac2c65bdb68e5d81cbf3b640862f710151f1b0a8e4d570753: done |++++++++++++++++++++++++++++++++++++++|
elapsed: 2.4 s total: 230.5 (96.0 MiB/s)
ctr: failed to read expected number of bytes: unexpected EOF
What version of containerd are you using?
1.6.19
Any other relevant information
runc --version
uname -a
5.10.179-171.711.amzn2.aarch64 #1 SMP Tue Jun 6 01:59:12 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
Show configuration if it is related to CRI plugin.
No response
The text was updated successfully, but these errors were encountered: