-
Notifications
You must be signed in to change notification settings - Fork 181
NFS-utils #857
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
NFS-utils #857
Conversation
| - | | ||
| mkdir -p /rootfs | ||
| mkdir -p /rootfs/usr/local/include/sys |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is an extra change? (it is already done in prepare: phase
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in the prepare: the folder that's created is /usr/local/include/sys, without the /rootfs prefix.
I however need the header file to be in the output of libtirpc to be able to reuse it.
storage/nfs-utils/rpc-statd.yaml
Outdated
| maskedPaths: [] | ||
| readonlyPaths: [] | ||
| mounts: | ||
| # netconfig file required by libtirpc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if these files doesn't need to be on the host, let's just put it into the container rootfs and stop using the mounts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good idea, I had not fully grasped the directory structure for extensions.
|
after some testing with https://gist.github.com/clementnuss/f292c0b190a987c111ac151232d565fc, I can confirm that the extension does it's job (as described in rpc-statd manual)
|
90a92a2 to
8735b91
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've addressed your comments, fixed a musl incompatibility, commented the patches and updated the author to PostFinance
for my part, this PR is ready. shall I squash my commits?
storage/nfs-utils/rpc-statd.yaml
Outdated
| maskedPaths: [] | ||
| readonlyPaths: [] | ||
| mounts: | ||
| # netconfig file required by libtirpc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good idea, I had not fully grasped the directory structure for extensions.
| - | | ||
| mkdir -p /rootfs | ||
| mkdir -p /rootfs/usr/local/include/sys |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in the prepare: the folder that's created is /usr/local/include/sys, without the /rootfs prefix.
I however need the header file to be in the output of libtirpc to be able to reuse it.
contains rpc.statd, needed to support locking with NFSv3 shares Signed-off-by: Andrey Smirnov <[email protected]> Signed-off-by: Clément Nussbaumer <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you, I tested this locally, and also Talos integration tests should pick it up so that it runs/starts
|
/m |
This extension brings in
rpcbindandrpc.statd(from the nfs-utils tools), two daemons required to mount NFS shares with locking support.using this extension makes it directly possible to use e.g. trident v25.06 to mount NFS shares with locks support. (NetApp/trident#806 (comment))
it would also solve the following issues: siderolabs/talos#6582 siderolabs/talos#8862
I set the TIER of the extension to contrib, but feel free to bump to extra if you think you want to help support the build process.
I could happily contribute some test cases, but I would require some guidance on where to implement those.