-
Notifications
You must be signed in to change notification settings - Fork 433
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
[Error] podman system check - layer content modified. Podman reports "damaged" layers, image, and containers after distrobox create #1656
Comments
I am not sure about this, also, you didn't start the container (and the removal of it keeps the error) During creation distrobox does not touch the image at all, it only performs a
While starting the container does modify the container itself, not the image layer |
I'm not sure either, are you able to reproduce it? I did a lot of narrowing-down to get a minimal reproduction scenario, and it turned out that starting the container is not necessary to cause this issue. This might not be a distrobox issue at all, and this Adapting the command you pasted for a new fedora 41 server install yields the same results! Interesting.
|
Apologies, here is the result with
|
I opened an issue at the podman project, since the command you shared makes me think it's not distrobox! |
I have not found any issues describing this yet.
Immediately after
distrobox create
,podman system check
claims my images and layers are damaged. I can still run the containers without any apparent issues. On the surface, the messages seem to suggest the mtime has changed. The hex values in the output can be sensibly interpreted as seconds since the epoch.My suspicion is that this looks like a big deal but actually isn't.
Logs for
distrobox create -v ...
andpodman --log-level=debug system check
attached.distrobox-create-verbose.log
distrobox-podman-system-check.log
Expected behavior
podman system check
does not yield errors afterdistrobox create
.distrobox create
and a subsequentdistrobox rm
does not have side effects (see Additional context, below)Desktop (please complete the following information):
podman 5.3.1
distrobox 1.8.0
Fedora 41 Server, installed into VM from ISO. This problem also occurs on Bluefin, which is where I first encountered it.
installed via
sudo dnf install -y distrobox
Additional context
This happens with every container image I've tried, for example
ghcr.io/ublue-os/fedora-toolbox
Interestingly, removing the distrobox does not correct the issue.
The text was updated successfully, but these errors were encountered: