nfs wont start on cockpit

[chipbreak]

installed cockpit using the helper script, then installed the 3x 45drive repos: identities, navigator & file_share.

when i go to install them i get an nfs error:

Creating config file /etc/default/nfs-kernel-server with new version

A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.
invoke-rc.d: initscript nfs-kernel-server, action "start" failed.
○ nfs-server.service - NFS server and services
Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; preset: enabled)
Active: inactive (dead)
 
Jan 08 15:14:14 cockpit systemd[1]: Dependency failed for nfs-server.service - NFS server and services.
Jan 08 15:14:14 cockpit systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.

is this because the cockpit script installs cockpit as an unprivileged container?

ive seen cockpit work as a privileged in version 7 of pve. currently trying in pve 8.3

will do more testing tonight without using the helper script.

[protonaut]

Same problem here.

Fresh installed helper script and installed identities, navigator & file_share.

[protonaut]

journalctl -xe produces the following massage:

░░ The job identifier is 723 and the job result is failed.
Mar 18 10:30:14 xxxx-cockpit systemd[1]: Dependency failed for rpc_pipefs.target.
░░ Subject: A start job for unit rpc_pipefs.target has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit rpc_pipefs.target has finished with a failure.
░░
░░ The job identifier is 722 and the job result is dependency.
Mar 18 10:30:14 xxxxx-cockpit systemd[1]: Dependency failed for rpc-gssd.service - RPC security service for NFS client and server.
░░ Subject: A start job for unit rpc-gssd.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit rpc-gssd.service has finished with a failure.
░░
░░ The job identifier is 721 and the job result is dependency.

[protonaut]

I found the solution: The error proceeds because the LXC Container was created unprivileged.
When I recreated the Container with elevated privileges everything went fine.

[protonaut]

I would appreciate if the helper-script returns a hint that NFS requires higher privileges to work.
Because all the other scripts of tteck/community I know run fully within the unprivileged version.

[tremor021]

What other scripts?

[protonaut]

I use: pihole, tailscale, vaultwarden, nginxproxymanager, nextcloudpi, jupyternotebook, tandoor, paperless, paperless-ai, wallos, trilium, guacamole, gotify ,homepage ,docker ,openwebui, cronicle, momos, homeassistent, web-check, uptimekuma, pbs, headscale, datacenter, changedetection.

I don't recall ever to have set any privileged status for any container.
But I like that the helper-scripts mostly give a lot of hints during the interactive process of the setup.

[tremor021]

this is very strange. so you're saying somehow your all unpriviledged containers mentioned can issue mount.nfs without a problem?

[protonaut]

Nope. I'm just saying that in my experience the helper-scripts give enough advise during the setup-process (in case somebody needs usb_passthrough) so there is usually no need to set up higher privileges. And I assumed that the script will warn the user that some features of the LXC will not work without proper setting of privileges.

Until now I 've never run into troubles before. And that isn't obvious at all. For example my unprivileged tailscale LXC can fully access the host-system which doesn't even have tailscale installed . First I couldn't believe it but there is no privileged access necessary.