-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 history gives wrong size #4916
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
Thanks for taking the time to open the issue, @lfarkas! Could you provide the requested info from the issue template? The most important part is the output from |
|
Looking into it now. There's clearly a bug. |
vrothberg
added a commit
to vrothberg/libpod
that referenced
this issue
Jan 29, 2020
Get the layer's size whether it relates to the first history entry or not. This fixes issues where the first entry would always be shown to be of size 0. Fixes: containers#4916 Signed-off-by: Valentin Rothberg <[email protected]>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 23, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
we use a very simple basic container image from ubi7-minimal and install live555 live555-tools. podman images show:
registry.access.redhat.com/ubi7-minimal latest 2b4f0d37c483 4 weeks ago 83 MB
while the two packages size: 1497835, 687984 (and we run in one line and run microdnf clean all). and the resulting image size:94.3 MB.
but why? how can i discover who fill up the image? than we try
why history report 0B size and then where is the missing 10MB?
The text was updated successfully, but these errors were encountered: