Skip to content
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

Make nydus-snapshotter capable to download artifacts itself. #439

Open
changweige opened this issue Mar 30, 2023 · 0 comments
Open

Make nydus-snapshotter capable to download artifacts itself. #439

changweige opened this issue Mar 30, 2023 · 0 comments

Comments

@changweige
Copy link
Member

We currently see more and more needs to let nydus-snapshotter download OCI artifacts on its own.

  1. Nydus-snapshotter can't start nydusd if containerd clients like ctr and nerdtcl are only pulling image rather than running a container. It's because nydus-snapshotter can only know where the meta file (bootstrap) is located after the Prepare operation for it. So nydus-snapshotter must wait for the wriable layer on top of it.

  2. Container download container image, decompress and untar it in an atomic way, which means nydus-snapshotter can't handle the tar files itself to eliminate the unnecessary untar operations.

Nydus-snapshotter's configuration on mirror hosts is already compatible with container'd, which means nydus-snapshotter can directly use use some of containerd's public packages and have capability to download artifacts from mirror registry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant