Hi reetp, I'm specifically addressing you because your use-case is exactly the case that I'm attempting to support in the "phase 1" of removing this annoying limitation: that is, when the home directories are located somewhere deeper under the /home directory (we are also working on fixing the generic case where the home directory is located elsewhere, but that looks like a bigger effort which will take more time).
I made a small change to snapd, to have it create the apparmor snippet mentioned in comment #6, and that seems to work for me: I do have a user whose home is
/home/folks/<user>/
and snapd created a file /etc/apparmor.d/tunables/home.d/snapd with the line
@{HOMEDIRS}+="/home/folks"
After a reboot (this should not be needed in the final version), I could install snaps and run them without issues. If a similar apparmor snippet does not work for you, can you please let me know what snaps are failing, and what errors messages you get?
Hi reetp, I'm specifically addressing you because your use-case is exactly the case that I'm attempting to support in the "phase 1" of removing this annoying limitation: that is, when the home directories are located somewhere deeper under the /home directory (we are also working on fixing the generic case where the home directory is located elsewhere, but that looks like a bigger effort which will take more time).
I made a small change to snapd, to have it create the apparmor snippet mentioned in comment #6, and that seems to work for me: I do have a user whose home is
/home/ folks/< user>/
and snapd created a file /etc/apparmor. d/tunables/ home.d/ snapd with the line
@{HOMEDIRS} +="/home/ folks"
After a reboot (this should not be needed in the final version), I could install snaps and run them without issues. If a similar apparmor snippet does not work for you, can you please let me know what snaps are failing, and what errors messages you get?