.fstab files generated by snapd for the content interface do not follow the snap.<snap name> scheme

[Zygmunt Krynicki]

Files are currently named /var/lib/snapd/mount/snap.unix-domain-client.unix-domain-client.fstab but should be per snap as @zyga told me.

Also I the .fstab file is generated for each app of a snap where it should be generated just ones for the whole snap:

$ ls -1 /var/lib/snapd/mount/snap.unix-domain-client.*
/var/lib/snapd/mount/snap.unix-domain-client.test.fstab
/var/lib/snapd/mount/snap.unix-domain-client.unix-domain-client.fstab
$ cat /snap/unix-domain-client/current/meta/snap.yaml
apps:
  test:
    command: command-test.wrapper
  unix-domain-client:
    command: command-unix-domain-client.wrapper
    plugs:
    - network
architectures:
- amd64
confinement: strict
description: |
  Simple Unix domain client example written in Go. The
  primary usage is to test sharing a socket between snaps
  from the same developer/publisher via the content interface.
grade: devel
name: unix-domain-client
plugs:
  content:
    content: socket-directory
    target: $SNAP_DATA/sockets
summary: Simple Unix domain client example written in Go.
version: '0.1'

This bug has been cloned from a github issue: https://github.com/snapcore/snapd/issues/2572

[Michael Vogt (mvo)]

AFAIK this bug is fixed and the files are per-snap now instead of per app.