maggesandClaude Sonnet 5
ca62577a8b
Create Container form: - GPU passthrough dropdown (AMD/Intel via /dev/dri detection, NVIDIA excluded since it needs a different runtime) - device paths strictly validated server-side against the host's own detected list. - Macvlan network support: selecting a macvlan network reveals a static IP field and hides port mappings (meaningless once the container has its own LAN address), matching Unraid Docker Manager's "Custom: br0" behavior. Networks panel gained a matching macvlan network-creation flow, with the parent-interface dropdown read from Unraid's own network.cfg so it lists exactly what Docker Manager itself offers. Containers panel: - Edit: reopens the create form pre-filled from the container's current config (image/ports/volumes/env/network/restart policy/GPU/static IP); saving stops+removes the old container and recreates it under the same settings, since podman/Docker have no in-place "modify" API for most of this. - Update: same stop/remove/recreate flow, but pulls the current image first. "Check for Updates" compares each in-use image's local digest against its origin registry (Docker Hub/GHCR/self-hosted registries all verified live) with no podman-side feature backing it - implemented via the registry's own HTTP API. A small log-modal shows progress for both actions instead of a silent wait. - Fixed a real bug hit live: PodmanClient's flat 15s HTTP timeout aborted real image pulls/container creates mid-request; bumped to 600s (nginx already allows up to 640s for this plugin's requests). Images panel: - "Prune unused" (removes every image with zero containers referencing it, not just dangling ones - confirmation copy says so explicitly since this is more aggressive than it sounds) and per-image "Tag". Also several real UI bugs found via live screenshots: unused-image prune having no visible effect until reloaded, table action-button columns drifting row to row (a bare "display:flex" on a <td> was fighting the table layout algorithm), Templates category badges dumping raw multi-tag strings from real Unraid templates, and low-contrast search/filter controls that were nearly invisible against the card background. 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.