You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently we are trying to enhance nydus-snapshotter with EROFS with tarfs mode, which can be used to:
speed up OCIv1 image handling
provide runtime data integrity for OCIv1 images
support data integrity for confidential containers
With this new features and requirements, nydus-snapshotter need to support different working modes as below:
<style>
</style>
Scenario
Kernel Device
Filesystem
Lazy Loading
Need Daemon
Shared Daemon
Lazy loading/data dedup for runC
fusedev
FUSE-RAFS
Yes
Yes
Optional
To be defined
fusedev
FUSE-RAFS
No
Yes
Optional
Lazy loading/data dedup for runC
fscache
EROFS on host
Yes
Yes
Must
Tarfs for runC/confidential containers
blockdev
EROFS on host/guest
No
No
N/A
Lazy loading for Kata/runD
nodev
EROFS in guest
Yes
No
N/A
Currently we useDaemonMode and FsDriver to control the working mode. We need to extend/refine the configuration file format to support new usage models. How about the new configuration format
Recently we are trying to enhance nydus-snapshotter with EROFS with tarfs mode, which can be used to:
With this new features and requirements, nydus-snapshotter need to support different working modes as below:
<style> </style>Currently we use
DaemonMode
andFsDriver
to control the working mode. We need to extend/refine the configuration file format to support new usage models. How about the new configuration formatDaemonMode
andFsDriver
will still be supported for backward compatibility and transition, and eventually will be deprecated in v1.0.The text was updated successfully, but these errors were encountered: