magges/unraid-podman

Fork 0

Files

T

maggesandClaude Sonnet 5 e2fefcdf9c

Build Packages / Build .txz packages (push) Failing after 9s

Details

Lint / ShellCheck (push) Failing after 43s

Details

Lint / Validate .plg XML (push) Successful in 10s

Details

Lint / EditorConfig (push) Failing after 6s

Details

Add reproducible build system, native Unraid plugin, and WebUI

- versions.env pins podman, conmon, crun, netavark, aardvark-dns, passt,
  and fuse-overlayfs to verified upstream source checksums; SlackBuild
  recipes, scripts/build-packages.sh, checksums.sh, release.sh, and
  update-versions.sh implement the reproducible pipeline; GitHub Actions
  workflows build in a Slackware container and publish releases without
  committing any binaries.

- plugin/podman.plg installs/updates/removes all eight packages (the
  seven components plus the plugin's own unraid-podman scaffolding
  package) via upgradepkg, using the official Unraid array-event hook
  mechanism (event/disks_mounted, event/stopping) instead of editing
  /boot/config/go. rc.podman and the sbin/ helper scripts implement
  storage creation, config seeding/sync, preflight checks, autostart
  with per-container Safe-Mode, and package verify/update/rollback.

- webui/plugins/podman implements the Dashboard, Containers, Pods,
  Images, Volumes, Networks, Logs, Terminal, Compose, and Settings
  panels against the approved mockup (webui/mockups/prototype.html),
  talking to podman system service exclusively via PodmanClient.php
  (libpod REST API over the Unix socket), with two documented
  exceptions: Terminal's one-shot exec model and Compose's use of the
  podman compose CLI, since libpod has no REST equivalent for either.

- docs/ARCHITECTURE.md and docs/ROADMAP.md record the design decisions
  and honest current status (syntax-checked, unit- and
  integration-tested against fake sockets/servers; not yet run against
  a real Unraid/Podman/Slackware system).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-07-11 10:51:14 +00:00

1.5 KiB

Raw Blame History

FAQ

Q: Does this replace Docker on Unraid? Not initially. Phase 1 runs Podman alongside Docker with fully separate storage, networking, and firewall rules. A later phase adds an option to disable Docker once feature parity is reached — see ROADMAP.md.

Q: Is this rootless or rootful Podman? Phase 1 is rootful only, matching Docker's current trust model on Unraid. Rootless is planned for a later phase — see ARCHITECTURE.md.

Q: Will my existing Docker containers/appdata work with Podman? Bind-mounted appdata under /mnt/user/appdata/... can generally be reused, but there is no automatic Docker→Podman template migration in Phase 1. See ARCHITECTURE.md, section 9 (Volumes).

Q: Why isn't there a WebUI yet? The MVP intentionally ships CLI-only to validate the persistence, packaging, and init model first, before investing in GUI work. See ARCHITECTURE.md, section 18.

Q: Why does this need a cache pool / dedicated disk instead of just using /mnt/user? Podman's overlay storage driver needs real filesystem semantics that the /mnt/user FUSE layer (shfs) doesn't reliably provide. See ARCHITECTURE.md, section 4.3.

Q: Is this affiliated with Unraid, Inc. or the Podman project? No. This is an independent, community-driven plugin project.

1.5 KiB Raw Blame History

FAQ

1.5 KiB

Raw Blame History