Cannot refresh snaps if home is in NFS with root_squash

Bug #1804281 reported by Santiago Castro
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Expired
Undecided
Unassigned

Bug Description

"snap refresh" fails to execute if /home is in an NFS with the root_squash option (comes by default) because it tries to update the /home/*/snap directory using the root user, which doesn't have permissions because of the option.

It could be worked around with no_root_squash, but this is insecure.

Revision history for this message
Santiago Castro (bryant1410) wrote :

I've found that if I move /home/*/snap outside NFS and make it a symlink, refresh works. However, running the snap doesn't: "cannot create user data directory: /home/[user]/snap/[snap_name]/[version]: Not a directory"

Revision history for this message
Santiago Castro (bryant1410) wrote :
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

Dear reporter, can you please check if the issue persists? I recall that we switched snapd to use the identity of the user when operating on user files. Perhaps this is fixed now?

Changed in snappy:
status: New → Incomplete
affects: snappy → snapd
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for snapd because there has been no activity for 60 days.]

Changed in snapd:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.