Pod panic due to invalid argument when using rafs version6 about nydus-snapshotter HOT 9 OPEN

hi, @imeoer , I will leave office tomorrow. There will be an another colleague to follow this issue.

from nydus-snapshotter.

@zewenying Thanks for the details, It seems be related to the fs version v6 format, could you describe the image content a little more?

from nydus-snapshotter.

@zewenying Thanks for the details, It seems be related to the fs version v6 format, could you describe the image content a little more?

Thanks for your reply. Could you please give me some tools to describe the image content? Because I don't know what kind of image content will help you to find out the problem.

from nydus-snapshotter.

@zewenying Try to validate your rafs v6 image by nydusify check --source $oci_image --target $nydus_image first (requires nydusify, nydus-image, nydusd are installed on your node). :)

from nydus-snapshotter.

@zewenying Try to validate your rafs v6 image by nydusify check --source $oci_image --target $nydus_image first (requires nydusify, nydus-image, nydusd are installed on your node). :)

Hi, here is the log. And I try to setRUST_BACKTRACE=1 to get more logs, but there are no more logs.

Tips:

1. I use an another nydus image which has the same problem to this one. But it passes the check. So it seems like that the registry of source image works well.

INFO[2024-05-13T12:00:05+08:00] Verifying filesystem for source and Nydus image
INFO[2024-05-13T12:01:03+08:00] Verified Nydus image $TARGETIMAGE

from nydus-snapshotter.

@zewenying It looks like rafs v6 has some fs issues, does rafs v5 always works on the nydusify check?

from nydus-snapshotter.

@zewenying It looks like rafs v6 has some fs issues, does rafs v5 always works on the nydusify check?

No. It does not pass the check with the same error.

from nydus-snapshotter.

@zewenying Sorry for the misunderstand, It appears that the TimeOut keyword in your log, maybe it's a registry/network issue.

from nydus-snapshotter.

@zewenying Sorry for the misunderstand, It appears that the TimeOut keyword in your log, maybe it's a registry/network issue.

I have tried another problem image which passed the check three days ago and it fails today. It seems like the registry does not work well.

from nydus-snapshotter.