-
Notifications
You must be signed in to change notification settings - Fork 99
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
Pod panic due to invalid argument when using rafs version6 #594
Comments
@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. |
@zewenying Try to validate your rafs v6 image by |
Hi, here is the log. And I try to set Tips:
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 |
@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. |
@zewenying Sorry for the misunderstand, It appears that the |
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. |
hi, @imeoer , I will leave office tomorrow. There will be an another colleague to follow this issue. |
Problem Description
Hi, I meet a problem when using Nydus format imgae to create a Pod. The problem is Pod will panic with the following logs.
Pod logs
Nydus-snapshotter logs:
error: failed to get chunk information
Version Information
nydus-snapshotter
v0.10.0
nydusify
nydus-image
nydusd
Workaround
Sol1: change rafs version from 6 to 5
nydusify(
v2.2.2
) convert uses version6 as nydus image format, set to 5, then panic will not occur.nydusify convert --fs-version 5 --source $sourceImage --target $targetImage
Sol2: remove nydus image on machine and recreate the Pod
Just remove the image, such like
crictl rmi {image}
Question
Apart from the mentioned two solutions, is there any other solution to solve the problem? The ideal solution is every Pod using a fixed version nydus image can run normally on the machine. Is it possible to do some code patches in nydusify(
v2.2.2
) to implement the ideal solution?Other Useful Information
Some other nydus images which are converted with fs-version6 can run normally on the same machine. At the same time, Pod using the mentioned image can run normally on other machines.
The text was updated successfully, but these errors were encountered: