-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Proposal for taking nydus store plugin as a non-core subproject #15249
Comments
Thanks for reaching out and for providing all the details, @imeoer! @containers/podman-maintainers WDYT? |
I am in favor of it as long as there is at least one maintainer for the project. @imeoer who would be the maintainer? If we agree to move forward, I can help to set up the repository here |
I am fine with this, as long as it has maintainers. I would also like to see it packaged up into Fedora and made easy to be used by Podman. |
@vrothberg @giuseppe @rhatdan @TomSweeneyRedHat Many thanks to all, we currently have an initial version and will continue to refine and add tests and documentation. @fatelei and @imeoer will be the initial maintainers, the repo name may be |
hello @imeoer to be be more clear, when we discussed this as a team, we wanted it to actually work with podman. how close are you to that? |
@baude Thanks for the reply, the current implementation allows podman to basically run the nydus image, here is a demo and simple documentation, currently we need to continue to enhance the stability, functionality, and additional testing and documentation, will reach production availability in the future. |
ok, excellent; @giuseppe i can also help as well. |
should I create a new repository or do you prefer if I move an existing project? If we go for a new repository, what should be its name? nydus-storage-plugin? |
created https://github.com/containers/nydus-storage-plugin and added both of you as admin. Welcome aboard! |
Thanks all! We are cleaning up the code and will push the initial version soon. cc @fatelei |
Nydus image is a container accelerated image format provided by the Dragonfly image-service project, which offers the ability to pull image data on demand, without waiting for the entire image pull to complete and then start the container. It has been in production and shown vast improvements over the OCI v1 image format in terms of container launching speed, image space, and network bandwidth efficiency, as well as data integrity. Nydus image can be flexibly configured as a FUSE-based user-space filesystem or in-kernel FS with nydus daemon in user-space:
Nydus has been running steadily for 3 years in Alibaba Cloud, Ant Group, and ByteDance, supporting large-scale container clusters and the creation of millions of containers per day, serving thousands of customers in various business fields.
Podman is a user-friendly container runtime, we'd like to make it support Nydus images as well, so we created the nydus store plugin project like stargz store plugin, the project implements an additional layer store plugin for CRI-O/Podman, so that nydus images can be mounted with lazy pulling. The plugin depends on additional layer store plugin feature, uses go fuse implementation to interact with podman in filesystem, and nydusd does the actual remote mount for nydus image.
Now we would like to ask the community's opinion if we can propose to make the nydus store plugin as a non-core subproject of the containers community, we believe that the donation to containers will attract more users and developers for nydus itself and bring much value to the containers community users.
Looking forward to any feedback, thanks!
The text was updated successfully, but these errors were encountered: