snap try fails on user ownership of files in the testing directory
Bug #1622685 reported by
Michael Hall
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Triaged
|
Undecided
|
Unassigned | ||
Bug Description
When testing a snap with "snap try ./prime" it will sometimes fail with permission denials because the files in $SNAP (./prime in this case) are owned by the user. If you create a .snap and install it the denials will stop because the files in $SNAP will be owned by root.
| tags: | added: snapd-interface |
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #1 |
| Changed in snappy: | |
| status: | New → Triaged |
| tags: | removed: snapd-interface |
| affects: | snappy → snapd |
To post a comment you must log in.
This can probably be traced back to the fact that the files are not matching various "owner" constraints in the apparmor profiles. I think we might explore either mounting the snap in a way that makes all files appear to be owned by root (if possible) or by generating a slightly different apparmor profile for try-mode snaps.