content interface, DENIED mounting $SNAP/mydir
kyle.nitzsche at canonical.com
Thu Mar 2 18:33:46 UTC 2017
I am trying to use the wifi-ap content sharing interface.
It is DENIED (see below) when I try to use a $SNAP directory.
It works when I instead use $SNAP_DATA directory for the content
sharing. But, I have to create that directory at run time: I can't
figure out so far how to create (from snapcraft.yaml) an empty dir in
$SNAP_COMMON or $SNAP_DATA at install time. (Knowing this would solve my
To auto connect the interface (via a store snap declaration), I suppose
the directory must be present at install time. So creating the dir at
run time does not seem sufficient for the auto-connect requirement.
== Details when trying to use SNAP dir for content sharing:
plugs: [control, content]
I connect my snap to the interface apparently successfully:
$ sudo snap connect serv:control wifi-ap:control
$ snap interfaces | grep serv | grep "wifi-ap:"
But the bind mount was DENIED:
Mar 02 18:01:02 localhost.localdomain kernel: audit: type=1400
audit(1488477662.292:350110): apparmor="DENIED" operation="mount"
info="failed srcname match" error=-13
pid=11461 comm="snap-confine" srcname="/var/snap/wifi-ap/94/sockets/"
Both wifi-ap snap and my snap seem to have the required directories:
$ ls /var/snap/wifi-ap/94/sockets/
knitzsche at localhost:~$ ls /snap/serv/x3/
bin command-run.wrapper command-scan.wrapper command-wifi-ap.wrapper
meta snap sockets
More information about the Snapcraft