-
Notifications
You must be signed in to change notification settings - Fork 3.8k
content: ensure root directory exists before checking fs-verity support #12416
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
Conversation
|
This is the git commit message. Feel free to use this in your commit |
4544a0a to
e0279b5
Compare
|
done thanks @fuweid |
7f49254 to
f49a85e
Compare
|
@estesp @AkihiroSuda can this pr be merged it's easy to review. |
|
can you help review this pr it's easy to review @samuelkarp |
f49a85e to
6c05f4e
Compare
mikebrow
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see questions and a nit on the warning msg
6c05f4e to
c244397
Compare
mikebrow
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
c244397 to
9c24363
Compare
6b5ceaf to
094eca6
Compare
|
done thanks @AkihiroSuda |
3da87e9 to
e5caf33
Compare
fc5c6ab to
7fe31f2
Compare
|
/retest |
|
@ningmingxiao: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
faf577e to
57f8fc9
Compare
|
can you merge this pr ? I can create another pr change its mod to 0700 because the permission issue is unrelated to this pr |
03e1fed to
502d5a8
Compare
af7f6a2 to
b244e1a
Compare
|
can this pr be merged too? The file io.containerd.content.v1.content or permisson default is 755 , If it's not safety enough I can create another pr change it to 0700. ping @fuweid |
Currently, fs-verity support detection fails on fresh containerd installations because the content store root directory (io.containerd.content.v1.content) doesn't exist yet. This directory is only created when pulling images, causing checker to always be false on new hosts. The IsSupported() function attempts to create a temporary directory within rootPath to test fs-verity support, but fails when rootPath doesn't exist, returning an error that is silently ignored. Fix this by ensuring the root directory exists before performing the fs-verity support check in NewLabeledStore(). Signed-off-by: ningmingxiao <ning.mingxiao@zte.com.cn>
b244e1a to
5f0f0dc
Compare
if containerd run on a new host supported must be false
because rootPath (io.containerd.content.v1.content) doesn't exist.
I find io.containerd.content.v1.content dir only be created when pull images.
@AkihiroSuda @mxpv @fuweid