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
Describe the bug
Pulling the container has always been not very fast (c.f. #2715), but was still acceptable in our use-case. However, since. v7.7.0 it almost takes forever to pull the container. So far the longest I've waited was 8h and the pull was still not complete. Up until v7.6.0 it took me about half an hour.
To Reproduce
Steps to reproduce the behavior:
Run podman pull docker.io/oxsecurity/megalinter:latest
Wait forever
P.S. I am running the podman command as a non-root user and use overlayfs as a storage driver.
Expected behavior
Pull the container within a reasonable time-frame.
Additional context
Tested on a Debian 12.4 system with x86 architecture as well as macOS Sonoma 14.2.1 arm64 architecture.
The text was updated successfully, but these errors were encountered:
8h for a pull doesn't make any sense, what else is happening? Is it a problem from our side (apart from the fact that the full image is indeed full, thus the reason we make smaller more specialized images for common use-cases)
@echoix I actually figured out that this was due to a wrong measurement of the tool I used to monitor my memory usage. I figured out that it was a memory problem and with more memory pulling the image takes about 10min-15min.
Describe the bug
Pulling the container has always been not very fast (c.f. #2715), but was still acceptable in our use-case. However, since.
v7.7.0
it almost takes forever to pull the container. So far the longest I've waited was 8h and the pull was still not complete. Up untilv7.6.0
it took me about half an hour.To Reproduce
Steps to reproduce the behavior:
podman pull docker.io/oxsecurity/megalinter:latest
P.S. I am running the podman command as a non-root user and use overlayfs as a storage driver.
Expected behavior
Pull the container within a reasonable time-frame.
Additional context
Tested on a Debian 12.4 system with x86 architecture as well as macOS Sonoma 14.2.1 arm64 architecture.
The text was updated successfully, but these errors were encountered: