-
unraid-podman v0.1.3
Stablereleased this
2026-07-13 01:36:13 +02:00 | 5 commits to main since this releaseInstall: paste into Unraid Plugins → Install Plugin:
https://git.mp-mueller.de/magges/unraid-podman/releases/download/v0.1.3/podman.plgAdded
- Settings: a "Podman Service" card with live status plus Start/Stop/Restart,
each shown in a progress log modal — diagnosing and recovering a podman
that failed to start no longer needs SSH/terminal access at all. - Settings: "Format a Disk for Podman Storage", for a single-disk system
with no cache pool. Only ever lists disks with no existing partition,
filesystem, or RAID/ZFS membership signature, and never the Unraid boot
flash — both excluded by multiple independent checks, not just one.
Formatted disks are remounted by UUID on every boot.
Fixed
STORAGE_PATHwas never auto-created, even when its parent (a real,
already-mounted cache pool) existed — only failed if genuinely nothing
was mounted at all. Root cause of a real "cannot reach the Podman API
socket" report on a fresh install with a perfectly normal cache pool.- Cache-busting for the WebUI's own JS/CSS never actually worked, at all,
the entire time — Unraid runs.pagePHP througheval(), and
__DIR__insideeval()'d code resolves to the eval() call site's
directory, not the plugin's. Every "hard refresh" this project's own
docs/commits ever recommended only worked because Ctrl+Shift+R bypasses
the browser cache directly, independent of this (broken) mechanism. - Settings' service status chip showed "Not running" immediately after a
successful Start, because the "is it running" check only recognized
rc.podman status's own wording, notstart/stop/restart's. - The Podman Service log showed
rc.podman's multi-line output as one
run-together paragraph (missingwhite-space: pre-wrapon the pane
itself, not just its per-line children).
Downloads
- Settings: a "Podman Service" card with live status plus Start/Stop/Restart,