Podman fails to complete pulling some images when they are nearly fully downloaded #5583
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
openshift-ci-robot
added
the
kind/bug
|
I've tried two more times on podman 1.8.2 and the issue persists, but once I got a different "unexpected EOF" error: |
|
Strange I was able to pull with no problem. |
|
Are you behind a proxy? |
Yes, pulling with docker works fine. But once I saw it saying "retrying in 5..4.. seconds" and then resuming the download. I'll see if it happens again and provide the full output. According to my router, the internet connection was stable during the download.
No. Edit: spelling |
|
Here is the full output of As you can see, the retry happened rather at the start of the download. |
|
I have no idea why, but after another reboot, the issue just magically disappeared. I'll reopen this if it happens again. |
|
Apparently the issue isn't gone. I get the same error when trying to pull an alpine image: |
|
I think there is something wrong with your system or your network, that is triggering a failure on the pull. |
|
Thousands of users are able to pull thousands of images, and are not seeing this issue. |
|
You're probably right. It just seemed strange to me that it always fails when it's almost finished and neither my router nor I'll try it on a different network. |
|
Docker is slightly more tolerant for network errors and apparently has a couple of retries even on quite random failures when pulling. We don't do that as we expect the network to be stable. I expect the pulling to succeed on a different network. @malte-v, feel free to comment here or open a new issue if you're still seeing these issues. |
|
@malte-v Did you find the cause? I'm getting the same problem now. |
|
@mbleichner Probably your network connection isn't all that stable, just like mine. I think Docker has a more tolerant retry policy compared to podman. |
|
@malte-v Yes, I know. Docker also has to retry a few times when pulling and sometimes fails eventually. I have no idea what could be the cause though. The connections to docker hub are the only ones that suffer from this problem. Everything else works fine. This happens on all our servers, so I'm pretty sure it's something network-related, but I have no clue where to look :( |
|
There is a PR to add retry with Podman. |
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I'm trying to pull the official Rust image from the Docker Hub using podman. Strangely, it encounters an error when the image is nearly fully downloaded. Here are some attempts that should illustrate the problem:
Command line output
Rootless:
With root:
This doesn't seem to be a network issue since Docker has no problem with pulling these images and other images, like redislabs/redisgraph, can be pulled by podman without any errors.
Steps to reproduce the issue:
$ [sudo] podman pull docker.io/rust:latestDescribe the results you received:
Podman encounters a "connection reset by peer" error when the image is nearly fully downloaded.
Describe the results you expected:
Podman pulls the image without any errors.
Output of
podman version:Output of
podman info --debug:Package info (e.g. output of
rpm -q podmanorapt list podman):Additional environment details (AWS, VirtualBox, physical, etc.):
My home workstation.
The text was updated successfully, but these errors were encountered: