-
Notifications
You must be signed in to change notification settings - Fork 206
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
NAS support #1632
Comments
It is better to mount NFS to the local directory and then configure nydus to use |
Hi @imeoer, Q1: Am I right in understanding that you're suggesting configuring the nydusd backend like so:
Where I have Some notes on the configuration:
Q2: If I assume my registry hosts are the only ones that are writing to the NFS share, am I correct in thinking that there won't be any trampling of state? Q3: I'm assuming that I can't avoid the duplication of the nydus metadata files that the container hosts will download from the registry? In other words, there's not a way for me to store those metadata files on NFS too? |
A1: Right, the |
Great, thanks again for your answers @imeoer . And for A2, yes, I did mean nydusd clients writing to the NFS store, it's good to have confirmation it uses it readonly. |
The files in |
The README claims:
But I can't find any documentation on what sort of network attached storage is supported. The configuration files indicates only local filesystems or block devices can be used, but is there existing support for using shared networked block volumes, NFS, or other similar technologies?
Many thanks
The text was updated successfully, but these errors were encountered: