[⬇️ Download] [📖 Website] [☸ Quick Start (Kubernetes)] [🤓 Quick Start (nerdctl)] [❓ FAQs & Troubleshooting]
Nydus implements a content-addressable file system on the RAFS format, which enhances the current OCI image specification by improving container launch speed, image space and network bandwidth efficiency, and data integrity.
The following Benchmarking results demonstrate that Nydus images significantly outperform OCI images in terms of container cold startup elapsed time on Containerd, particularly as the OCI image size increases.
Provide Fast, Secure And Easy Access to Data Distribution
- Performance: Second-level container startup speed, millisecond-level function computation code package loading speed.
- Low Cost: Written in memory-safed language
Rust, numerous optimizations help improve memory, CPU, and network consumption. - Flexible: Supports container runtimes such as runC and Kata, and provides Confidential Containers and vulnerability scanning capabilities
- Security: End to end data integrity check, Supply Chain Attack can be detected and avoided at runtime.
- On-demand Load: Container images/packages are downloaded on-demand in chunk unit to boost startup.
- Chunk Deduplication: Chunk level data de-duplication cross-layer or cross-image to reduce storage, transport, and memory cost.
- Compatible with Ecosystem: Storage backend support with Registry, OSS, NAS, Shared Disk, and P2P service. Compatible with the OCI images, and provide native eStargz images support.
- Data Analyzability: Record accesses, data layout optimization, prefetch, IO amplification, abnormal behavior detection.
- POSIX Compatibility: In-Kernel EROFS or FUSE filesystems together with overlayfs provide full POSIX compatibility
- I/O optimization: Use merged filesystem tree, data prefetching and User I/O amplification to reduce read latency and improve user I/O performance.
| Tool | Description |
|---|---|
| nydusd | Nydus user-space daemon, it processes all fscache/FUSE messages from the kernel and parses Nydus images to fullfil those requests |
| nydus-image | Convert a single layer of OCI format container image into a nydus format container image generating meta part file and data part file respectively |
| nydusify | It pulls OCI image down and unpack it, invokes nydus-image create to convert image and then pushes the converted image back to registry and data storage |
| nydusctl | Nydusd CLI client (nydus-image inspect), query daemon's working status/metrics and configure it |
| ctr-remote | An enhanced containerd CLI tool enable nydus support with containerd ctr |
| nydus-docker-graphdriver | [Experimental] Works as a docker remote graph driver to control how images and containers are stored and managed |
| nydus-overlayfs | Containerd mount helper to invoke overlayfs mount with tweaking mount options a bit. So nydus prerequisites can be passed to vm-based runtime |
| nydus-backend-proxy | A simple HTTP server to serve local directory as a blob backend for nydusd |
| Type | Platform | Description | Status |
|---|---|---|---|
| Storage | Registry/OSS/S3/NAS | Support for OCI-compatible distribution implementations such as Docker Hub, Harbor, Github GHCR, Aliyun ACR, NAS, and Aliyun OSS-like object storage service | ✅ |
| Storage/Build | Harbor | Provides a general service for Harbor to support acceleration image conversion based on kinds of accelerator like Nydus and eStargz etc | ✅ |
| Distribution | Dragonfly | Improve the runtime performance of Nydus image even further with the Dragonfly P2P data distribution system | ✅ |
| Build | Buildkit | Provides the ability to build and export Nydus images directly from Dockerfile | ✅ |
| Build/Runtime | Nerdctl | The containerd client to build or run (requires nydus snapshotter) Nydus image | ✅ |
| Runtime | Docker / Moby | Run Nydus image in Docker container with containerd and nydus-snapshotter | ✅ |
| Runtime | Kubernetes | Run Nydus image using CRI interface | ✅ |
| Runtime | Containerd | Nydus Snapshotter, a containerd remote plugin to run Nydus image | ✅ |
| Runtime | CRI-O / Podman | Run Nydus image with CRI-O or Podman | 🚧 |
| Runtime | KataContainers | Run Nydus image in KataContainers as a native solution | ✅ |
| Runtime | EROFS | Run Nydus image directly in-kernel EROFS for even greater performance improvement | ✅ |
# build debug binary
make
# build release binary
make release
# build static binary with docker
make docker-staticConvert OCIv1 image to Nydus image: Nydusify, Acceld or Nerdctl.
Build Nydus image from Dockerfile directly: Buildkit.
Build Nydus layer from various sources: Nydus Image Builder.
To further reduce container startup time, a nydus image with a prefetch list can be built using the NRI plugin (containerd >=1.7): Container Image Optimizer
For more details on how to lazily start a container with nydus-snapshotter and nydus image on Kubernetes nodes or locally use nerdctl rather than CRI, please refer to Nydus Setup
Nydus-snapshotter is a non-core sub-project of containerd.
Check out its code and tutorial from Nydus-snapshotter repository.
It works as a containerd remote snapshotter to help setup container rootfs with nydus images, which handles nydus image format when necessary. When running without nydus images, it is identical to the containerd's builtin overlayfs snapshotter.
Normally, users do not need to start nydusd by hand. It is started by nydus-snapshotter when a container rootfs is prepared.
Run Nydusd Daemon to serve Nydus image: Nydusd.
In-kernel EROFS has been fully compatible with RAFS v6 image format since Linux 5.16. In other words, uncompressed RAFS v6 images can be mounted over block devices since then.
Since Linux 5.19, EROFS has added a new file-based caching (fscache) backend. In this way, compressed RAFS v6 images can be mounted directly with fscache subsystem, even such images are partially available. estargz can be converted on the fly and mounted in this way too.
Guide to running Nydus with fscache: Nydus-fscache
Nydus is deeply integrated with Dragonfly P2P system, which can greatly reduce the network latency and the single point pressure of the registry server. Benchmarking results in the production environment demonstrate that using Dragonfly can reduce network latency by more than 80%, to understand the performance results and integration steps, please refer to the nydus integration.
If you want to deploy Dragonfly and Nydus at the same time through Helm, please refer to the Quick Start.
Nydus is able to generate a tiny artifact called a nydus zran from an existing OCI image in the short time. This artifact can be used to accelerate the container boot time without the need for a full image conversion. For more information, please see the documentation.
Nydus provides a variety of methods to support running on docker(Moby), please refer to Nydus Setup for Docker(Moby) Environment
Nydus can also run with macfuse(a.k.a osxfuse). For more details please read nydus with macOS.
The containerd remote snapshotter plugin nydus-snapshotter can be used to run nydus images, or to run eStargz images directly by appending --enable-stargz command line option.
In the future, zstd::chunked can work in this way as well.
Using the key features of nydus as native in your project without preparing and invoking nydusd deliberately, nydus-service helps to reuse the core services of nyuds.
Nydus aims to form a vendor-neutral opensource image distribution solution to all communities. Questions, bug reports, technical discussion, feature requests and contribution are always welcomed!
We're very pleased to hear your use cases any time. Feel free to reach us via Slack or Dingtalk.
-
Slack: Nydus Workspace
-
Twitter: @dragonfly_oss
-
Dingtalk: 34971767
- Technical Meeting: Every Wednesday at 06:00 UTC (Beijing, Shanghai 14:00), please see our HackMD page for more information.