Open mskarbek opened 3 years ago
Error's coming out of c/common image library, but I suspect it's hiding a real error from c/storage. @vrothberg PTAL
trying to reuse blob sha256:5576786dd32999d193c0a8e82b1235611131c8128404af9999195884a9d3be9e at destination: reading layer "dce1852f14fde9fa55fb420d688640efc747b7be931c00c11fe444aabfde63b0" for blob "sha256:5f70bf18a086007016e948b04aed3b82103a36bea41755b6cddfaf10ace3c6ef": error creating zfs mount: mount b51d7037-4cc1-4ad9-9e50-b533fd87b24e/datafs/var/lib/containers/dce1852f14fde9fa55fb420d688640efc747b7be931c00c11fe444aabfde63b0:/var/lib/containers/storage/zfs/graph/dce1852f14fde9fa55fb420d688640efc747b7be931c00c11fe444aabfde63b0: no such file or directory
Probably ZFS related which I have absolutely no experience in. @giuseppe, do you have advice?
We have no clue and little experience with zfs, I would recommend you switch to Overlay,
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Occasionally
podman
fails to load image with error:Let's say I have a few images to load from archives:
At some point, ZFS driver just fails unexpectedly:
Debug log from a single occurrence of the error:
Working solution for now is to remove
podman
storage db/configuration by either destroying each container/image dataset andrm -rf
everything inside/var/lib/containers
or simply destroying the whole dataset mounted as/var/lib/containers
and create fresh empty one.podman
can work weeks, months without issue on one host, this is sporadic and hard to reliably reproduce. I was looking for a good trigger of this behavior but unsuccessfully for now, reporting this for feature reference.Steps to reproduce the issue:
Use
podman
for some timeTry to load image from archive
Describe the results you received:
podman
fails to load image from archiveDescribe the results you expected:
podman
loads image from archive without issuesAdditional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.): Independent of host type, observed on bare metal, KVM, VMWare, AWS. Observed on Fedora (32, 33, 34) and RHEL 8. OpenZFS 2.0.x and 2.1.x.