It looks like snap-confine has no way of checking that the fstab mnt entries generated by the snapd mount security backend have been changed or removed.
Probably easier to have snapd call snap-discard-ns on any content i/f connects/disconnects.
It looks like snap-confine has no way of checking that the fstab mnt entries generated by the snapd mount security backend have been changed or removed.
Probably easier to have snapd call snap-discard-ns on any content i/f connects/ disconnects.