[Bug]: Disk Collector reporting tmpfs /run (1.5GB) instead of actual storage mount #373
Description
Issue Category
Installation/Setup
Bug Description
The storage display in the Command Center shows 2.5 MB / 1.5 GB instead of the
actual available storage. The disk-collector container is incorrectly reporting
the tmpfs /host/run filesystem (1.5GB) instead of the actual /storage mount.
When running "docker exec nomad_disk_collector df -h" the output clearly shows:
- /dev/sdb1 at /storage = 915.8G available (CORRECT drive)
- tmpfs at /host/run = 1.5G (INCORRECTLY reported in UI)
The UI shows exactly 1.5GB which matches the tmpfs /host/run, not the
915GB /storage mount.
Steps to Reproduce
- Install Project NOMAD on a system where /storage is mounted on a separate
drive from the OS - Open Command Center in browser
- Navigate to Apps > Maps or any add-on
- Observe Storage shows 2.5 MB / 1.5 GB instead of actual drive size
Expected Behavior
- Install Project NOMAD on a system where /storage is mounted on a separate
drive from the OS - Open Command Center in browser
- Navigate to Apps > Maps or any add-on
- Observe Storage shows 2.5 MB / 1.5 GB instead of actual drive size
Actual Behavior
Storage displays 2.5 MB / 1.5 GB which matches the tmpfs /host/run filesystem
N.O.M.A.D. Version
- NOMAD Version: 1.29.1 - OS: Zorin OS 17 (Ubuntu 24.04 Noble base) - Kernel: 6.17.0-19-generic - Docker: CE 29.3.0 - Storage: /storage mounted on separate 1TB HDD (/dev/sdb1) - Boot drive: 931GB NVMe SSD (/dev/nvme0n1)
Operating System
Ubuntu 24.04
Docker Version
No response
Do you have a dedicated GPU?
Yes
GPU Model (if applicable)
No response
System Specifications
No response
Service Status (if relevant)
No response
Relevant Logs
Browser Console Errors (if UI issue)
Screenshots
No response
Additional Context
docker exec nomad_disk_collector df -h output:
Filesystem Size Used Available Use% Mounted on
/dev/sdb1 915.8G 204.9M 869.0G 0% /storage <- CORRECT
tmpfs 1.5G 2.5M 1.5G 0% /host/run <- UI shows this
The disk-collector appears to be selecting the wrong filesystem when
calculating available storage space. It may be picking the first tmpfs
that matches a size threshold, or incorrectly parsing the mount table
when storage is on a separate physical drive.
Workaround: None found. The symlink approach (/opt/project-nomad/storage
-> /data/nomad-storage) does not resolve the issue.
Pre-submission Checklist
- I have searched for existing issues that might be related to this bug
- I am running the latest version of Project N.O.M.A.D. (or have noted my version above)
- I have redacted any personal or sensitive information from logs and screenshots
- This issue is NOT related to running N.O.M.A.D. on an unsupported/non-Debian-based OS