Some quirks with the mounts/disks

[jc21]

Firstly, fantastic work :) I myself was literally days away from starting a project just like this in golang myself. I hope it takes off. Love the space invaders too!

Describe the bug
I'm running this in Docker on 3 different hosts, amd64, arm64 and riscv64. For the most part, everything is working. The "disk space" widget isn't quite right to me, at least.

On all these hosts, I'm using the same docker-compose.yml

services:

  kula:
    container_name: kula
    image: c0m4r/kula:latest
    restart: unless-stopped
    volumes:
      - '/proc:/proc:ro'
      - './data:/app/data'
    network_mode: host

NanoPi R6s - FriendlyWRT OS

Actual storage:

❯ df -h
Filesystem       Size  Used Avail Use% Mounted on
tmpfs            512K     0  512K   0% /dev
tmpfs            793M  1.2M  792M   1% /run
overlay          995M  520M  409M  56% /
tmpfs            3.9G   39M  3.9G   1% /tmp
/dev/mmcblk2p10   27G  120M   25G   1% /opt

Raspberry Pi 5 - Raspbian OS

Actual storage:

╭───────────────────────────────────────────────────────────────────────────────────────────────╮
│ 3 local devices                                                                               │
├────────────┬────────┬────────┬────────┬───────────────────────────────┬──────┬────────────────┤
│ MOUNTED ON │   SIZE │   USED │  AVAIL │              USE%             │ TYPE │ FILESYSTEM     │
├────────────┼────────┼────────┼────────┼───────────────────────────────┼──────┼────────────────┤
│ /          │ 234.6G │  16.9G │ 208.1G │ [#...................]   7.2% │ ext4 │ /dev/mmcblk0p2 │
│ /mnt/2tb-1 │   1.8T │ 785.4G │   1.1T │ [########............]  42.2% │ xfs  │ /dev/sda1      │
│ /mnt/2tb-2 │   1.8T │ 695.9G │   1.1T │ [#######.............]  37.4% │ xfs  │ /dev/sdb1      │
╰────────────┴────────┴────────┴────────┴───────────────────────────────┴──────┴────────────────╯

Note

The /app/data mount here is stored on one of the 2tb drives.

Intel CPU - Rocky Linux 9

Actual storage:

╭─────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ 14 local devices                                                                                    │
├────────────────┬────────┬────────┬────────┬────────────────────────────┬──────┬─────────────────────┤
│ MOUNTED ON     │   SIZE │   USED │  AVAIL │            USE%            │ TYPE │ FILESYSTEM          │
├────────────────┼────────┼────────┼────────┼────────────────────────────┼──────┼─────────────────────┤
│ /              │ 459.5G │ 267.2G │ 192.3G │ ███████████▌         58.2% │ xfs  │ /dev/rl_taurus/root │
│ /mnt/1tb-ssd-1 │ 931.1G │ 645.6G │ 285.5G │ █████████████▌       69.3% │ xfs  │ /dev/sda1           │
│ /mnt/240-ssd-1 │ 223.5G │ 164.2G │  59.3G │ ██████████████▌      73.5% │ xfs  │ /dev/sdb1           │
│ /mnt/240-ssd-2 │ 223.5G │ 105.7G │ 117.8G │ █████████            47.3% │ xfs  │ /dev/sdc1           │
│ /mnt/2tb-1     │   1.8T │   1.8T │  68.1G │ ███████████████████  96.3% │ xfs  │ /dev/sdk1           │
│ /mnt/4tb-1     │   3.6T │   3.5T │ 155.1G │ ███████████████████  95.8% │ xfs  │ /dev/sde1           │
│ /mnt/4tb-2     │   3.6T │   3.2T │ 453.6G │ █████████████████▌   87.8% │ xfs  │ /dev/sdf1           │
│ /mnt/4tb-3     │   3.6T │   3.5T │ 162.8G │ ███████████████████  95.6% │ xfs  │ /dev/sdh1           │
│ /mnt/4tb-6     │   3.6T │   3.6T │  38.3G │ ███████████████████▌ 99.0% │ xfs  │ /dev/sdl1           │
│ /mnt/6tb-1     │   5.5T │ 936.2G │   4.5T │ ███                  16.8% │ xfs  │ /dev/sdm1           │
│ /mnt/8tb-1     │   7.3T │   6.8T │ 495.2G │ ██████████████████▌  93.4% │ xfs  │ /dev/sdj1           │
│ /mnt/8tb-2     │   7.3T │   7.1T │ 206.6G │ ███████████████████  97.2% │ xfs  │ /dev/sdg1           │
│ /mnt/8tb-3     │   7.3T │   6.7T │ 539.6G │ ██████████████████▌  92.8% │ xfs  │ /dev/sdi1           │
│ /mnt/8tb-4     │   7.3T │   4.9T │   2.4T │ █████████████        67.0% │ xfs  │ /dev/sdd1           │
╰────────────────┴────────┴────────┴────────┴────────────────────────────┴──────┴─────────────────────╯

Expected behavior

I'd expect not to see /etc/resolv.conf

I know too well how friggin' hard it is to get the disk info from the OS within a docker container. Even CasaOS installs a helper on the info on this. That said it would be GREAT if we could get all the combined storage total/use/free in one graph that acurately represents the server.

[c0m4r]

Thank you for you report and kind words, I really appreciate it and great to hear you like it!
This part of Kula definitely still needs work. Fixing docker mounts should be fairly easy, but supporting multiple drives is not trivial indeed. I think it needs to be implemented in small steps. I'll start with simple solutions and then improve it further.

[c0m4r]

Quick docker fix 189138e

[c0m4r]

I just pushed a new version of the Docker image (0.7.4). This should improve things, but of course more work still needs to be done.

[jc21]

Great that part is working as expected thanks :)

[c0m4r]

Thanks for the heads up! I'll let you know when more improvements ships.

[c0m4r]

initial multi disk and network interfaces support: 3c58338

Kula should now detect multiple drives and network interfaces, and let you switch between them.
You can also override the auto-detection, which isn't and probably never will be perfect, in the config:

# Data collection settings
collection:
  # You can override the auto-detected list of disks and network interfaces by uncommenting and populating these lists:
  # devices: ["sda", "nvme0n1"]
  # mountpoints: ["/", "/mnt/data"]
  # interfaces: ["eth0", "wlan0"]

[c0m4r]

New release is ready. When you have a moment, please test it and let me know what you think. Fingers crossed :)

[jc21]

Thanks for the changes, here's my findings. I don't think they are working as you expect yet. Also not sure how to switch between things? Either it's not obvious or not available because it's still only detecting 1 disk.

❯ ls -la /dev/disk/by-uuid/
total 0
0 lrwxrwxrwx 1 root root 15 Jan  1  1970 21724cc6-e5a3-48a1-8643-7917dba3a9fb -> ../../mmcblk0p2
0 lrwxrwxrwx 1 root root 10 Dec  5 00:46 76bd2f83-f383-4b58-b768-3c40e7a087ed -> ../../sdb1
0 lrwxrwxrwx 1 root root 11 Dec  5 00:46 c39c0388-46b4-4308-916a-9aaad96f35be -> ../../zram0
0 lrwxrwxrwx 1 root root 10 Jan  1  1970 cb691a92-4ec5-467b-8a85-916ae6347f7c -> ../../sda1
0 lrwxrwxrwx 1 root root 15 Jan  1  1970 EACA-13DA -> ../../mmcblk0p1

❯ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            3.9G     0  3.9G   0% /dev
tmpfs           1.6G   61M  1.6G   4% /run
/dev/mmcblk0p2  235G   17G  209G   8% /
tmpfs           4.0G     0  4.0G   0% /dev/shm
tmpfs           5.0M   48K  5.0M   1% /run/lock
tmpfs           4.0G     0  4.0G   0% /tmp
/dev/mmcblk0p1  510M   66M  445M  13% /boot/firmware
tmpfs           1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs           1.0M     0  1.0M   0% /run/credentials/serial-getty@ttyAMA10.service
/dev/sda1       1.9T  787G  1.1T  43% /mnt/2tb-1
/dev/sdb1       1.9T  696G  1.2T  38% /mnt/2tb-2
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs           807M   64K  807M   1% /run/user/1000

config.yaml - and I know it's mounted and working because I changed the hostname and saw that reflected in the interface

collection:
  interval: 1s
  devices: ["mmcblk0p2", "sda1", "sdb1"]
  mountpoints: ["/", "/mnt/2tb-1", "/mnt/2tb-2"]

Let me know if you need more OS info. If you have a static IP I can whitelist you and give you access to the UI.

[jc21]

I should have mentioned this one is the arm64 Debian Raspberry Pi 5.

The amd64 Rocky Linux 9 host, without any custom config, detects the devices correctly and I can see how to switch. However it doesn't detect the disks/space correctly, only showing / and /app/data

[c0m4r]

Thanks for the feedback.

Accessing the UI probably won't help me. Shell access would be helpful, but of course that's out of the question :) I'd rather have similarly custom environments with various mountpoint formats and multiple drives. I used to have more of these, but lately I've mostly had standardized, simple setups at my fingertips.

There are currently several filters and exceptions in the code that may be too restrictive. I think I'll start by adding debugging so that Kula logs which devices and mountpoints it detects and which it ignores/skips and why. It will then probably become easier to get to the bottom of this.

[c0m4r]

For additional information, the output from /proc/mounts would be useful (you can filter it to show only those devices that should be detected) so I can see the file system used and the mounting method.

[jc21]

ok here you go:

/dev/mmcblk0p2 / ext4 rw,noatime 0 0
/dev/sda1 /mnt/2tb-1 xfs rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/sdb1 /mnt/2tb-2 xfs rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/sda1 /docker xfs rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0

Note that the last one is not something I would want to show but you won't be able to filter it out either. It's a hard mount I use for simplicity:

UUID=cb691a92-4ec5-467b-8a85-916ae6347f7c /mnt/2tb-1       xfs    defaults,nofail         0 2
/mnt/2tb-1/docker-data                    /docker          none   defaults,bind,nofail    0 0

UUID=76bd2f83-f383-4b58-b768-3c40e7a087ed /mnt/2tb-2       xfs    defaults,nofail         0 2

[c0m4r]

No worries, I also use a lot of not-so-beautiful workarounds. Besides I see nothing wrong here.