I have been having success with manual mounting (using security.syscalls.intercept.mount options) but now not with udisks2+polkit:
$ udisksctl mount -b /dev/disk/by-uuid/41eea4a1-b2d0-48ad-8b40-0240c9e08dda
Error looking up object for device /dev/disk/by-uuid/41eea4a1-b2d0-48ad-8b40-0240c9e08dda
Having,
$ ls -l /dev/disk/by-uuid/41eea4a1-b2d0-48ad-8b40-0240c9e08dda
brw-rw----. 1 root disk 8, 1 Jan 10 17:26 /dev/disk/by-uuid/41eea4a1-b2d0-48ad-8b40-0240c9e08dda
and,
part_41eea4a1-b2d0-48ad-8b40-0240c9e08dda:
required: "false"
source: /dev/disk/by-uuid/41eea4a1-b2d0-48ad-8b40-0240c9e08dda
type: unix-block
which is saddening.
udisks2’s journal:
(sdg3 is the host’s FS and where the storage pool of the containers are stored as defined by THE default profile; there’s these entries repeating)
Jan 10 21:31:54 dmaincomp udisksd[237]: Error statting /dev/sdg3: No such file or directory
Jan 10 21:31:54 dmaincomp udisksd[237]: Error statting /dev/sdg3: No such file or directory
Jan 10 21:31:54 dmaincomp udisksd[237]: Error statting /dev/sdg3: No such file or directory
Jan 10 21:31:54 dmaincomp udisksd[237]: Error statting /dev/sdg3: No such file or directory
Jan 10 21:31:54 dmaincomp udisksd[237]: Error statting /dev/sdg3: No such file or directory
Jan 10 21:31:54 dmaincomp udisksd[237]: Error statting none: No such file or directory