The mount-control interface allows the mounting and unmounting of both transient (non-persistent) and persistent filesystem mount points. The interface does not itself create or maintain mount points, but instead permits the snapped application or service to create and maintain its own.
This interface gives privileged access to the device.
Requires snapd version 2.54+.
See Interface management and Supported interfaces for further details on how interfaces are used.
Developer details
Auto-connect: no
Super-privileged: yes
Attributes:
-
persistent(plug): defines whether the mount can be persistent or not.
Eithertrueorfalse. Defaults tofalse. -
type(plug): lists one or more acceptable filesystems for this mount.
Example:[ext2, ext3, ext4] -
what(plug): absolute path of what to mount using a matching wildcard.
Example:/dev/sd* -
where(plug): either an absolute destination path for the mount, or a starting reference to$SNAP_COMMONor$SNAP_DATAoptionally followed by a path. Wildcards are also supported.
Example:/media/$USER/** -
options(plug, required): a list of one or more permitted options.
Example:[rw, sync]
-
namespace(plug): eithersnap, for locations within the snap,host, for locations outside the snap, orautoto set the namespace according to the where pattern. Defaults toauto.
See AppArmor globbing syntax for details on how the pattern matching and wildcards work.
It’s the responsibility of the snapped application or service to create and maintain a mount point, using either of the following:
- the mount command
- the mount() system call
- an accompanying snapctl mount
The snapctl mount command is the only option for creating a persistent mount point via its --persistent mount option.
Accepted filesystems
Most filesystem types which are supported by the host system are allowed by this interface, with a few exceptions.
The following filesystems are not accepted:
bpf, cgroup, cgroup2, debugfs, devpts, encryptfs, hugetlbfs, overlayfs, proc, securityfs, sysfs, and tracefs.
While other filesystems are accepted, the following filesystems are supported along with their respective filesystem-specific mount options (more on mount options below):
adfs, affs, aufs, autofs, btrfs, cifs, ext2, ext3, ext4, fat, functionfs, fuse, hfs, hpfs, iso9660, jfs, msdos, nfs, nfs4, ntfs, ntfs-3g, lowntfs-3g, ramfs, reiserfs, squashfs, tmpfs, ubifs, udf, ufs, umsdos, usbfs, vfat, xfs, and zfs.
Note: If only tmpfs is specified, what must be none.
Permitted mount options
The following filesystem-independent mount options are permitted:
async, atime, auto, bind, defaults, diratime, dirsync, iversion, lazytime, noatime, noauto, nodev, nodiratime, noexec, nofail, nogroup, noiversion, nolazytime, nomand, noowner, norelatime, nosuid, nostrictatime, nouser, nousers, relatime, ro, rw, strictatime, and sync.
Note: Option bind is only allowed when no filesystem is specified.
Filesystem-specific mount options are also permitted, so long as each is supported by every filesystem listed in the corresponding type section. The mount options supported by a given filesystem can usually be found in its respective manpage or in the mount manpage. The complete list of supported filesystem-specific mount options for each filesystem type is included in the source code for this interface.
Code examples
plugs:
mntctl:
interface: mount-control
mount:
- what: /dev/sd*
where: /media/**
type: [ext2, ext3, ext4]
options: [rw, sync, user_xattr]
- what: /usr/**
where: $SNAP_COMMON/**
options: [bind]
- what: /dev/sda{0,1}
where: $SNAP_COMMON/**
options: [ro]
- what: /dev/sdb[0-1]
where: $SNAP_COMMON/{foo,other,**}
options: [sync]
apps:
app:
plugs: [mntctl]
The test code can be found in the snapd repository: https://github.com/snapcore/snapd/blob/master/interfaces/builtin/mount_control_test.go
The source code for the interface is in the snapd repository: https://github.com/snapcore/snapd/blob/master/interfaces/builtin/mount_control.go
