SYSTEMD-MOUNTFSD(8)
π SYSTEMD-MOUNTFSD.SERVICE π
okay bestie, so this page is from the systemd-mountfsd.service manual β it's literally the disk image file system mount service and it's about to be your new fave. no cap. β¨
πΈ SYNOPSIS πΈ
systemd-mountfsd.service
/usr/lib/systemd/systemd-mountfsd
π¦ DESCRIPTION π¦
okay so systemd-mountfsd is this iconic system service that literally dissects disk images and hands back mount file descriptors for all the file systems inside them to clients, all via a Varlink IPC API. it's giving "middleware but make it slay." π
the disk images you feed it must contain a raw file system image, or they have to follow the UAPI.2 Discoverable Partitions Specification<sup>1</sup>. and before it even thinks about mounting anything, it checks that the disk image is legit β authenticity gets established in one of these ways (or a combo, periodt):
- if the disk image is sitting in a regular file in one of these directories β
/var/lib/machines/,/var/lib/portables/,/var/lib/extensions/,/var/lib/confexts/β or their counterparts in/etc/,/run/,/usr/lib/β then it's assumed to be trusted. like, you're in the VIP section, you're good. π - if the disk image contains a Verity enabled disk image, plus a signature partition with a key in the kernel keyring or in
/etc/verity.d/*.crt(and related directories), then the disk image is considered trusted. but bestie, real talk β note that the GPT partition table of the disk image gets parsed by the kernel to discover its contents, andsystemd-mountfsdjust assumes the GPT parser is robust against malformed input and applies no security policies or checks around it. so like, it's trusting the kernel to not fumble the bag. π
this service provides one Varlink<sup>2</sup> service: io.systemd.MountFileSystem β it accepts a file descriptor to a regular file or block device, and returns a number of file descriptors referring to an fsmount() file descriptor that the client can then attach to a path of their choice. literally choose your own adventure. β¨
the returned mounts are automatically allowlisted in the per-user-namespace allowlist maintained by systemd-nsresourced.service(8). yes, they get the stamp of approval. π
and the file systems are automatically fsck(8)'ed before mounting. safety first, bestie. π«Ά
π₯ SEE ALSO π₯
β NOTES β
- UAPI.2 Discoverable Partitions Specification β https://uapi-group.org/specifications/specs/discoverable_partitions_specification/
- Varlink β https://varlink.org/
π okay that's the whole page bestie, you ate that. now go mount some disk images responsibly. mwah. π
made with love by systemd 261.3 π systemd-mountfsd.service(8) era β slay responsibly, iykyk π
π¦ where this page comes from
- ubuntu stonking: systemd-container 261.3-0ubuntu3 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms