SikamikanikoBG/homelab-monitor v0.29.1

v0.29.1 — patch: shared container data stops landing on one container's bill

on GitHub

Patch release — bug fix, rolled up into the next minor. Shipped quietly: no announcement, but the in-app updater will offer it.

Fixed

• Shared data is no longer billed to one container just because nobody else named the same path. The "more than one container can write this" check compared mount sources as strings, so it only caught two containers naming the same directory. It missed the nested case: one container mounting /srv/models while others mount / — what toolbox and distrobox do, at /run/host — write the same bytes under two different strings, so the whole tree was charged to the one container that named it. A container stopped for two weeks with a 40.9 kB writable layer was reported at 1.25 TB. Sharing is now decided by path coverage rather than string equality, and one-directional on purpose: a container with 500 GB under /srv/media keeps being billed for it when another mounts only /srv/media/photos. When a parent mount does take data out of the count, the collector says so in the log rather than letting the disk column empty itself in silence.

Found, diagnosed and fixed by @andreahaku — his fourth contribution here. Thank you. (#264/#265)

Update: docker compose pull && docker compose up -d, or use the dashboard's one-click self-update.