mountPoint type
You can configure mountPoint in one of two ways:
-
Structured Format: Use
idType,options, andpathfields for a more detailed configuration.mountPoint: path: /boot/efi options: umask=0077 idType: part-uuid -
Shorthand Path Format: Provide the mount path directly as a string when only
pathis required.mountPoint: /boot/efiIn this shorthand format, only the
pathis specified, and default values will be applied to any optional fields.
Added in v0.3.
idType [string]
Default: part-uuid
The partition ID type that should be used to recognize the partition on the disk.
Supported options:
-
uuid: The filesystem’s partition UUID. -
part-uuid: The partition UUID specified in the partition table. -
part-label: The partition label specified in the partition table.
Example:
storage:
disks:
- partitionTableType: gpt
partitions:
- id: esp
type: esp
size: 8M
- id: rootfs
size: 2G
label: root
- id: var
size: 2G
label: var
bootType: efi
filesystems:
- deviceId: esp
type: fat32
mountPoint:
path: /boot/efi
options: umask=0077
- deviceId: rootfs
type: ext4
mountPoint:
path: /
idType: part-label
- deviceId: var
type: ext4
mountPoint:
path: /var
idType: part-label
os:
bootloader:
resetType: hard-reset
Added in v0.3.
options [string]
The additional options used when mounting the file system or BTRFS subvolume.
These options are in the same format as
mount’s
-o option or the fs_mntops field of the
fstab file.
When specifying a BTRFS subvolume’s mount options, the subvol= and subvolid= mount options cannot be specified,
since the tool automatically includes subvol= based on the subvolume’s path.
Added in v0.3.
path [string]
Required.
The absolute path of where the file system or BTRFS subvolume should be mounted.
The mounts will be sorted to ensure that parent directories are mounted before child
directories.
For example, /boot will be mounted before /boot/efi.
Added in v0.3.