ubuntu-core-launcher apparmor denial when creating /tmp/snaps
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snap-confine |
Fix Released
|
Undecided
|
Unassigned | ||
15.04 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
...or "/tmp/snaps not writeable after installing webdm"
NOTE: Not sure if this is specific to webdm or when snappy installs any 'framework' before /tmp/snaps is created.
Steps to reproduce:
1) 'sudo snappy install webdm' on a fresh snappy unit
2) 'ls -al /tmp/snaps' - root only write perms
3) 'sudo snappy install hello-world'
4) 'hello-world.echo'
Expected result: "Hello World!"
Actual result: mkdir: cannot create directory ‘/tmp/snaps/
Example: http://
If hello-world is installed first (and so creates /tmp/snaps with ubuntu:ubuntu) then there's no issue: http://
I found a reference to the issue on the mailing list, but didn't see an existing bug report although experienced the same issue today: https:/
Related branches
- John Lenton (community): Approve
-
Diff: 26 lines (+7/-1)2 files modifieddebian/changelog (+6/-0)
debian/usr.bin.ubuntu-core-launcher (+1/-1)
- John Lenton (community): Approve
-
Diff: 26 lines (+4/-1)2 files modifieddebian/changelog (+3/-0)
debian/usr.bin.ubuntu-core-launcher (+1/-1)
no longer affects: | snappy |
This is because the launcher has this in its policy:
/tmp/snap.*/ w,
It should have this instead: snap{s, .*}/ w,
/tmp/