-
Notifications
You must be signed in to change notification settings - Fork 204
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
podman push image got Error: unexpected EOF #2123
Comments
Does this always stop at the same point if you try again, that is:
? |
Yes |
Same here on
Always failing at the same point. |
Are you both using podman machine? |
Looks like the memory footprint increased:
I recreated the VM with 4GB of RAM (
|
|
@mtrmac PTAL |
Thanks @Vringe for the workaround. I set the memory to 6GB and that solved the problem. |
Is Compare containers/storage#2055 . |
Hmm, nope I checked I actually just installed podman yesterday from the standard homebrew formula without changing anything at all. |
In the machine VM.
I am not sure why we still ship the wrong config files in the podman-next copr. My assumption was that this should only be set on rawhide/f41. |
I agree. |
zstd:chunked should follow distro policies and no blanket handling for all copr envs. Resolves: containers#2123 Signed-off-by: Lokesh Mandvekar <[email protected]>
Given we ship podman-next copr packages on quite a few envs now, config file handling should follow distro policy as much as possible. Resolves: containers#2123 Signed-off-by: Lokesh Mandvekar <[email protected]>
From my side, the issue is resolved after upgrading Podman to 5.2.5. I have to delete the VM, recreate it so that it uses the new Podman. Meaning all the existing images have to be re-created, and that will solve the problem. |
Issue Description
When pushing an image to a remote repository
e.g. podman push icr.io/.....
the command will fail with
Error: unexpected EOF
This worked in version 4.9.3
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
The command failed with
Describe the results you expected
I expect the push would succeed. This fails on 5.2.0 but worked with 4.9.3.
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: