mirror of
https://github.com/Crosstalk-Solutions/project-nomad.git
synced 2026-03-28 03:29:25 +01:00
The disk-collector could produce an empty fsSize array when /host/proc/1/mounts is unreadable, causing the admin UI to fall back to systeminformation's fsSize which includes tmpfs mounts. This led to the storage display showing ~1.5 GB (tmpfs /run) instead of the actual storage capacity. Two changes: - disk-collector: fall back to df on /storage when host mount table yields no real filesystems, since /storage is always bind-mounted from the host and reflects the actual backing device. - easy-setup UI: when falling back to systeminformation fsSize, filter for /dev/ block devices and prefer the largest one instead of blindly taking the first entry. Fixes #373 |
||
|---|---|---|
| .. | ||
| sidecar-disk-collector | ||
| sidecar-updater | ||
| collect_disk_info.sh | ||
| entrypoint.sh | ||
| install_nomad.sh | ||
| management_compose.yaml | ||
| migrate-disk-collector.md | ||
| migrate-disk-collector.sh | ||
| run_updater_fixes.sh | ||
| start_nomad.sh | ||
| stop_nomad.sh | ||
| uninstall_nomad.sh | ||
| update_nomad.sh | ||
| wikipedia_en_100_mini_2025-06.zim | ||