skipped attributes
| status |
attribute |
duration |
| skipped local |
checks.aarch64-darwin.jsonTypes
- The legacy table is outdated and should not be used. We recommend using the gpt type instead.
Please note that certain features, such as the test framework, may not function properly with the legacy table type.
If you encounter errors similar to:
"error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times,"
this is likely due to the use of the legacy table type.
for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
|
— |
| skipped local |
checks.aarch64-linux.jsonTypes
- The legacy table is outdated and should not be used. We recommend using the gpt type instead.
Please note that certain features, such as the test framework, may not function properly with the legacy table type.
If you encounter errors similar to:
"error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times,"
this is likely due to the use of the legacy table type.
for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
|
— |
| skipped local |
checks.x86_64-linux.jsonTypes
- The legacy table is outdated and should not be used. We recommend using the gpt type instead.
Please note that certain features, such as the test framework, may not function properly with the legacy table type.
If you encounter errors similar to:
"error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times,"
this is likely due to the use of the legacy table type.
for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
|
— |
| skipped local |
checks.x86_64-linux.legacy-table
- The legacy table is outdated and should not be used. We recommend using the gpt type instead.
Please note that certain features, such as the test framework, may not function properly with the legacy table type.
If you encounter errors similar to:
"error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times,"
this is likely due to the use of the legacy table type.
for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
- The legacy table is outdated and should not be used. We recommend using the gpt type instead.
Please note that certain features, such as the test framework, may not function properly with the legacy table type.
If you encounter errors similar to:
"error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times,"
this is likely due to the use of the legacy table type.
for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
|
— |
| skipped local |
checks.x86_64-linux.legacy-table-with-whitespace
- The legacy table is outdated and should not be used. We recommend using the gpt type instead.
Please note that certain features, such as the test framework, may not function properly with the legacy table type.
If you encounter errors similar to:
"error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times,"
this is likely due to the use of the legacy table type.
for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
- The legacy table is outdated and should not be used. We recommend using the gpt type instead.
Please note that certain features, such as the test framework, may not function properly with the legacy table type.
If you encounter errors similar to:
"error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times,"
this is likely due to the use of the legacy table type.
for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
|
— |
| skipped local |
checks.x86_64-linux.mdadm-btrfs-wipe
- mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
|
— |
| skipped local |
checks.x86_64-linux.standalone
- The legacy table is outdated and should not be used. We recommend using the gpt type instead.
Please note that certain features, such as the test framework, may not function properly with the legacy table type.
If you encounter errors similar to:
"error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times,"
this is likely due to the use of the legacy table type.
for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
- the create output is deprecated and will be removed, please open an issue if you're using it!
- The legacy table is outdated and should not be used. We recommend using the gpt type instead.
Please note that certain features, such as the test framework, may not function properly with the legacy table type.
If you encounter errors similar to:
"error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times,"
this is likely due to the use of the legacy table type.
for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
- the mount output is deprecated and will be removed, please open an issue if you're using it!
- The legacy table is outdated and should not be used. We recommend using the gpt type instead.
Please note that certain features, such as the test framework, may not function properly with the legacy table type.
If you encounter errors similar to:
"error: The option `disko.devices.disk.disk1.content.partitions."[definition 1-entry 1]".content._config` is read-only, but it's set multiple times,"
this is likely due to the use of the legacy table type.
for a migration you can follow the guide at https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md
|
— |
| skipped local |
checks.aarch64-darwin.checkJqSyntax
|
— |
| skipped local |
checks.aarch64-linux.checkJqSyntax
|
— |
| skipped local |
checks.x86_64-linux.bcachefs
|
— |
| skipped local |
checks.x86_64-linux.boot-raid1
|
— |
| skipped local |
checks.x86_64-linux.btrfs-only-root-subvolume
|
— |
| skipped local |
checks.x86_64-linux.btrfs-subvolumes
|
— |
| skipped local |
checks.x86_64-linux.checkJqSyntax
|
— |
| skipped local |
checks.x86_64-linux.cli
|
— |
| skipped local |
checks.x86_64-linux.complex
|
— |
| skipped local |
checks.x86_64-linux.f2fs
|
— |
| skipped local |
checks.x86_64-linux.gpt-bios-compat
|
— |
| skipped local |
checks.x86_64-linux.gpt-name-with-special-chars
|
— |
| skipped local |
checks.x86_64-linux.gpt-unformatted
|
— |
| skipped local |
checks.x86_64-linux.hybrid
|
— |
| skipped local |
checks.x86_64-linux.hybrid-mbr
|
— |
| skipped local |
checks.x86_64-linux.hybrid-tmpfs-on-root
|
— |
| skipped local |
checks.x86_64-linux.long-device-name
|
— |
| skipped local |
checks.x86_64-linux.luks-btrfs-raid
|
— |
| skipped local |
checks.x86_64-linux.luks-btrfs-subvolumes
|
— |
| skipped local |
checks.x86_64-linux.luks-detached-header
|
— |
| skipped local |
checks.x86_64-linux.luks-fido2
|
— |
| skipped local |
checks.x86_64-linux.luks-interactive-login
|
— |
| skipped local |
checks.x86_64-linux.luks-lvm
|
— |
| skipped local |
checks.x86_64-linux.luks-multiple
|
— |
| skipped local |
checks.x86_64-linux.luks-on-mdadm
|
— |
| skipped local |
checks.x86_64-linux.luks-password-mismatch
|
— |
| skipped local |
checks.x86_64-linux.lvm-raid
|
— |
| skipped local |
checks.x86_64-linux.lvm-sizes-sort
|
— |
| skipped local |
checks.x86_64-linux.lvm-thin
|
— |
| skipped local |
checks.x86_64-linux.make-disk-image
|
— |
| skipped local |
checks.x86_64-linux.make-disk-image-impure
|
— |
| skipped local |
checks.x86_64-linux.mdadm
|
— |
| skipped local |
checks.x86_64-linux.mdadm-raid0
|
— |
| skipped local |
checks.x86_64-linux.mdadm-raid5-args
|
— |
| skipped local |
checks.x86_64-linux.module
|
— |
| skipped local |
checks.x86_64-linux.multi-device-no-deps
|
— |
| skipped local |
checks.x86_64-linux.negative-size
|
— |
| skipped local |
checks.x86_64-linux.non-root-zfs
|
— |
| skipped local |
checks.x86_64-linux.simple-efi
|
— |
| skipped local |
checks.x86_64-linux.swap
|
— |
| skipped local |
checks.x86_64-linux.tmpfs
|
— |
| skipped local |
checks.x86_64-linux.vm-with-disko-swap
|
— |
| skipped local |
checks.x86_64-linux.with-lib
|
— |
| skipped local |
checks.x86_64-linux.xfs
|
— |
| skipped local |
checks.x86_64-linux.zfs
|
— |
| skipped local |
checks.x86_64-linux.zfs-encrypted-root
|
— |
| skipped local |
checks.x86_64-linux.zfs-over-legacy
|
— |
| skipped local |
checks.x86_64-linux.zfs-with-vdevs
|
— |