1. I already had @{HOMEDIRS}+=/home/*/ and I did not forget to reload.
However, the audit message still refers to /home/r/, which is the actual
parent directory of my home directory.2. Including #include <abstractions/nameservice> directly below /usr/lib/snapd/snap-confine flags=(attach_disconnected) works. It don't seems to be necessary to include #include <abstractions/base> Adding network inet and network inet6 solves the problem as well. Snaps without network interface: Right, they don't work. A workaround is to install them in devmode. Enabling network access for all snaps just to make them compatible with NFS don't seems to be a perfect solution from the security perspective. Doesn't that mean, that these snaps can access every network service, not only NFS? Is it possible to explicitly enable NFS (and other network file systems) and not enable network access for all kinds of services? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662552 Title: snaps don't work with NFS home /home/u/user.name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
