github-starred/komodo
2
0
Fork 1
mirror of https://github.com/moghtech/komodo.git synced 2026-07-16 11:12:09 -05:00
Code Issues 12.0k Packages Projects Releases 104 Wiki Activity

[GH-ISSUE #679] Better explanation for disk mounts #2360

New Issue
Closed
opened 2026-04-11 10:17:13 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-11 10:17:13 -05:00
Owner
Copy Link

Originally created by @Lenart12 on GitHub (Jul 23, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/679

Hi, I have found the documentation for disk mounts lacking and I'm wondering if it can be improved/if im even doing it right because I have spent a long time figuring it out and even now I'm not sure I got it right.

Here is how I configured it:

# Create an empty file in each partition
# First find the UUID for each disk
root@orange:/nvme1/app/komodo# blkid
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="8F3E-64CA" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="8d0bb902-1cd9-4024-8c71-2c1763172aac"
/dev/mmcblk0p2: LABEL="rootfs" UUID="a380dbdb-d74d-454c-9882-629b11b597c4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="f496ef64-4e2a-420b-9b98-4304a617a654"
/dev/sda: UUID="b4b8b78a-8990-435f-9a10-024dbd2eab62" UUID_SUB="98fe5f9c-d8a7-4713-b89f-67b1b4507e35" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/zram1: LABEL="log2ram" UUID="5d48b22a-679c-44d5-8bb9-c19a59eb789a" BLOCK_SIZE="4096" TYPE="ext4"
/dev/zram0: UUID="9cc24f57-ba96-4407-ba91-c58ead79b3c5" TYPE="swap"
# rootfs
root@orange:/nvme1/app/komodo# touch /.disk-a380dbdb-d74d-454c-9882-629b11b597c4
# my nvme
root@orange:/nvme1/app/komodo# touch /nvme1/data/.disk-b4b8b78a-8990-435f-9a10-024dbd2eab62

Then mount it in periphery:

  periphery:
    volumes:
      ## Disk
      - /etc/hostname:/etc/hostname:ro
      - /.disk-a380dbdb-d74d-454c-9882-629b11b597c4:/disk/a380dbdb-d74d-454c-9882-629b11b597c4:ro
      - /nvme1/data/.disk-b4b8b78a-8990-435f-9a10-024dbd2eab62:/disk/b4b8b78a-8990-435f-9a10-024dbd2eab62:ro

And add it in compose.env:

## If the disk size is overreporting, can use one of these to
## whitelist / blacklist the disks to filter them, whichever is easier.
## Accepts comma separated list of paths.
## Usually whitelisting just /etc/hostname gives correct size.
PERIPHERY_INCLUDE_DISK_MOUNTS=/disk/a380dbdb-d74d-454c-9882-629b11b597c4,/disk/b4b8b78a-8990-435f-9a10-024dbd2eab62
# PERIPHERY_EXCLUDE_DISK_MOUNTS=/snap,/etc/repos

This seems like im over complicating things...

Another thing is that to me it seems that its misnamed - by looking at the code its actually checking the filesystem usage, which would make more sense.

Edit:
Since I figured out its actually filesystem not disks I have simplified it a bit:

PERIPHERY_INCLUDE_DISK_MOUNTS=/usage/rootfs,/usage/nvme1

and

periphery:
    volumes:
      ## Disk
      - /etc/hostname:/etc/hostname:ro
      - /etc/hostname:/usage/rootfs:ro # Mount point /
      - /nvme1/app/komodo/.kdm:/usage/nvme1:ro # Mount point /nvme1

(though I still had to create a dummy .kdm file but I suppose I could use some other file that I would expect to never change)

Originally created by @Lenart12 on GitHub (Jul 23, 2025). Original GitHub issue: https://github.com/moghtech/komodo/issues/679 Hi, I have found the documentation for disk mounts lacking and I'm wondering if it can be improved/if im even doing it right because I have spent a long time figuring it out and even now I'm not sure I got it right. Here is how I configured it: ```sh # Create an empty file in each partition # First find the UUID for each disk root@orange:/nvme1/app/komodo# blkid /dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="8F3E-64CA" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="8d0bb902-1cd9-4024-8c71-2c1763172aac" /dev/mmcblk0p2: LABEL="rootfs" UUID="a380dbdb-d74d-454c-9882-629b11b597c4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="f496ef64-4e2a-420b-9b98-4304a617a654" /dev/sda: UUID="b4b8b78a-8990-435f-9a10-024dbd2eab62" UUID_SUB="98fe5f9c-d8a7-4713-b89f-67b1b4507e35" BLOCK_SIZE="4096" TYPE="btrfs" /dev/zram1: LABEL="log2ram" UUID="5d48b22a-679c-44d5-8bb9-c19a59eb789a" BLOCK_SIZE="4096" TYPE="ext4" /dev/zram0: UUID="9cc24f57-ba96-4407-ba91-c58ead79b3c5" TYPE="swap" # rootfs root@orange:/nvme1/app/komodo# touch /.disk-a380dbdb-d74d-454c-9882-629b11b597c4 # my nvme root@orange:/nvme1/app/komodo# touch /nvme1/data/.disk-b4b8b78a-8990-435f-9a10-024dbd2eab62 ``` Then mount it in periphery: ```yaml periphery: volumes: ## Disk - /etc/hostname:/etc/hostname:ro - /.disk-a380dbdb-d74d-454c-9882-629b11b597c4:/disk/a380dbdb-d74d-454c-9882-629b11b597c4:ro - /nvme1/data/.disk-b4b8b78a-8990-435f-9a10-024dbd2eab62:/disk/b4b8b78a-8990-435f-9a10-024dbd2eab62:ro ``` And add it in compose.env: ```ini ## If the disk size is overreporting, can use one of these to ## whitelist / blacklist the disks to filter them, whichever is easier. ## Accepts comma separated list of paths. ## Usually whitelisting just /etc/hostname gives correct size. PERIPHERY_INCLUDE_DISK_MOUNTS=/disk/a380dbdb-d74d-454c-9882-629b11b597c4,/disk/b4b8b78a-8990-435f-9a10-024dbd2eab62 # PERIPHERY_EXCLUDE_DISK_MOUNTS=/snap,/etc/repos ``` This seems like im over complicating things... Another thing is that to me it seems that its misnamed - by looking at the code its actually checking the filesystem usage, which would make more sense. Edit: Since I figured out its actually filesystem not disks I have simplified it a bit: ```sh PERIPHERY_INCLUDE_DISK_MOUNTS=/usage/rootfs,/usage/nvme1 ``` and ```yaml periphery: volumes: ## Disk - /etc/hostname:/etc/hostname:ro - /etc/hostname:/usage/rootfs:ro # Mount point / - /nvme1/app/komodo/.kdm:/usage/nvme1:ro # Mount point /nvme1 ``` (though I still had to create a dummy .kdm file but I suppose I could use some other file that I would expect to never change)
GiteaMirror added the setupdocumentation labels 2026-04-11 10:17:13 -05:00
GiteaMirror commented 2026-04-11 10:17:14 -05:00
Author
Owner
Copy Link

@mbecker20 commented on GitHub (Jul 24, 2025):

If you can run it outside docker like via systemd, it is much better at simply detecting the disks as they are, you don't need to do anything

<!-- gh-comment-id:3111932638 --> @mbecker20 commented on GitHub (Jul 24, 2025): If you can run it outside docker like via systemd, it is much better at simply detecting the disks as they are, you don't need to do anything
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
1.19.0
1.19.1
1.19.2
1.19.3
1.19.4
2.0.0
bug
documentation
done
enhancement
help wanted
info
pull-request
Mirrored from GitHub Pull Request
 question
security
seen 👀
setup
thinking 🤔
ui
v2
No Label documentation setup
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#2360
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?