I have now stumbled across this bug again. In addition to the “root_squash” option for nfs, as long as NFSv4 with sec=krb5 is not enabled, we were able to start it successfully by setting the home folder to g+x. We don't understand why, but similar to the previous speaker and +rx by other, we consider this solution unacceptable.
We find it incomprehensible that a system that appears to place such a high priority on security requires the use of unacceptable, insecure permissions in order to run in production environments. Especially since it is being forced upon us. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973321 Title: snaps don't start when current working directory is on a remote FS (sshfs, NFS) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1973321/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
