maggesandClaude Sonnet 5
23898ff62e
Dashboard: - Plain-count stat tiles (Running/Stopped/Pods/Images/Volumes/Networks) separated from a single "Resource Usage" card (CPU/Memory/Swap/Storage meter rows) instead of forcing both into one tile grid, which produced awkward spanning-tile/dead-cell layouts. - Fixed CPU usage never changing (libpod's own cpuUtilization is computed once and never resampled) by computing it from /proc/stat deltas instead. - Fixed memory usage reading far too high by using /proc/meminfo's MemAvailable instead of libpod's raw (non-reclaimable-aware) memFree. - Added an Autostart Queue table reusing podman-autostart.sh's own failure-counter files. - Dashboard and Containers now auto-refresh every ~2s (paused when the tab is hidden or a modal is open). Toasts: - Real success/warn/error/info toast notifications replacing every alert() used for one-way feedback, across every panel. Container detail modal: - 5 new tabs: Resources, Logs, Console, Events, Healthcheck. Containers panel: - Folders to group containers (name + icon), stored in the plugin's own folders.json — a folder's header always shows an icon+name+status chip per member, matching Unraid's own Docker page folders. "Move to Folder" becomes "Remove from Folder" once a container is already grouped. - Containers can carry an icon URL and a WebUI URL (small button next to the name), both stored as container labels and auto-filled from templates where applicable. - Settings: an "Add container" control for the Autostart order table. Fixes: - Context menus now measure their own rendered size and flip above the anchor when there isn't room below, instead of running off-screen. - Containers table now uses table-layout:fixed with explicit column widths — auto layout was shifting every column (and the header) on every folder expand/collapse, and briefly again when a flex wrapper was mistakenly placed directly on a <td>. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
unraid-podman
A native Unraid plugin that integrates Podman as a first-class container engine, running alongside Docker.
Status: architecture / scaffolding stage. No functional code has been shipped yet. This repository currently defines the target structure and design; see docs/ARCHITECTURE.md for the full technical plan and docs/ROADMAP.md for what's coming.
Goals
- Run rootful Podman on Unraid with full persistence across reboots (config, images, containers, volumes, networks) despite Unraid's RAM-root design.
- Coexist cleanly with Docker — no shared storage, network, or firewall conflicts.
- Follow Unraid's native conventions:
.plginstallation, Slackware.txzpackages, BSD-stylerc.dinit scripts (no systemd), config on/boot, data on the array/cache. - Provide a WebUI in the Dynamix style once the CLI-driven core is stable.
- Eventually make Docker optional/disable-able once feature parity is reached.
See docs/ARCHITECTURE.md for the full rationale behind every decision below.
Repository structure
.
├── .github/ CI workflows, issue/PR templates, community health files
├── assets/ Icons, screenshots, branding used by the plugin & GUI
├── config/ Default containers/storage/registries config templates
├── docs/ Architecture, install guide, FAQ, troubleshooting, roadmap
├── packages/ Slackware .txz build recipes (podman, conmon, crun, netavark, ...)
├── plugin/ The .plg manifest, rc.d init script, sbin helper scripts,
│ and the default files deployed to /boot/config/plugins/podman
├── scripts/ Build, release, and developer tooling scripts
└── webui/ Dynamix-style WebUI pages (plugins/podman/), added in a later phase
Installation
Not yet available. Once packages and the .plg manifest are published, installation
will be the standard Unraid flow: Plugins → Install Plugin with the .plg URL, or
via the Unraid Community Applications store once listed there.
Documentation
- Architecture — full technical design (directory layout, packaging, init scripts, persistence, networking, autostart, updates, rollback, logging, error handling, future WebUI).
- Roadmap — phased delivery plan.
- Install guide — end-user installation steps (draft).
- Troubleshooting — common problems and diagnostics.
- FAQ
Contributing
Contributions are welcome — see CONTRIBUTING.md for the dev workflow, coding conventions, and how the packaging pipeline works. Please also review our Code of Conduct.
Security
Rootful Podman's API socket is root-equivalent. See SECURITY.md for the vulnerability disclosure process and known security considerations.
License
Licensed under the MIT License.