-
Notifications
You must be signed in to change notification settings - Fork 642
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
docs: add nydus snapshotter description #1189
Conversation
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.
Thanks
@@ -0,0 +1,26 @@ | |||
# Lazy-pulling using Nydus Snapshotter | |||
|
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.
| :zap: Requirement | nerdctl >= 0.22 |
|-------------------|----------------|
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.
(And kernel version, maybe?)
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.
@AkihiroSuda Thanks for the reply, the kernel version is not mandatory if users don't use the in-kernel EROFS backend (added below).
At present, nerdctl run has supported nydus snapshotter, this commit adds description in doc. Signed-off-by: Yan Song <yansong.ys@antfin.com>
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.
Yet not quite sure the CI fails, could we just ignore it or trigger again?
At present,
nerdctl run
has supported nydus snapshotter, this PR adds description in doc.Signed-off-by: Yan Song yansong.ys@antfin.com