8 Commits

Include renames

Author	SHA1	Message	Date
maggesandClaude Sonnet 5	d931d8e9e9	release: v0.1.5 ... Fixes a real bug in scripts/release.sh's per-package entity matching found while cutting this release: "podman"'s own glob also matched podman-compose's file (podman is a literal prefix of podman-compose), and find | head -n1's unsorted output order let podman-compose's package silently win the "podman" entity on this run. Now explicitly skips any match that actually belongs to a different, more specific component name also in the COMPONENTS list. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-13 21:53:59 +00:00
maggesandClaude Sonnet 5	166f0d96d1	release: v0.1.3 ... Built and verified via Gitea Actions (build-packages.yml run 124, commit 9b9d1a0, all 11 packages succeeded). Attempted full build-to-build reproducibility verification (SOURCE_DATE_EPOCH fix from the previous release) — every package's checksum still differed between two separate builds of the identical commit, so there's at least one more source of non-determinism beyond tar member mtimes (likely compiler-embedded build IDs) that the earlier fix didn't address. Given that, this release was cut and published the same way v0.1.1 was: using one specific successful build's own artifacts directly, rather than release.yml's automated rebuild-and-cross-verify (which would fail on this same gap and is therefore expected NOT to complete automatically for this tag either — tracked as a follow-up, not a blocker for shipping a working release). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-12 23:36:13 +00:00
maggesandClaude Sonnet 5	80e006c73f	release: v0.1.1 - fix plugin.plg <URL>/<MD5> formatting bug ... v0.1.0's <URL>/<MD5> entity values were split across their own lines inside the tags. Unraid's plugin manager (scripts/plugin, see download()) passes that raw text straight into a `wget ... -O $name $url` shell command without trimming whitespace, so the leading newline split the command in two: wget got no URL argument ("wget: missing URL") and the URL text itself ran as a separate, failing shell command ("sh: line 2: https://...: No such file or directory") — which the installer then reported as "download failure: zero-length file", looking like a network problem when it was a formatting bug. Confirmed live: v0.1.0 fails to install on a real Unraid host (reproduced via the plugin manager's own CLI, scripts/plugin install, not just the webGUI). Every real Unraid plugin keeps <URL>...</URL> on one line (verified against unassigned.devices.plg on the same host) — this fix matches that convention. Package contents are unchanged from v0.1.0; only podman.plg's XML formatting and the version/baseURL entities are bumped. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-12 22:14:59 +00:00
maggesandClaude Sonnet 5	b91bdb9810	release: v0.1.0 ... First cut release, built and verified via Gitea Actions (build-packages.yml run against commit 18b414d, all 11 packages succeeded). Repo lives on Gitea (git.mp-mueller.de), not GitHub — scripts/release.sh and plugin/podman.plg's github/gitURL/supportURL/baseURL entities are updated to point there instead of the GitHub placeholders they had before (this project has never actually had a GitHub remote). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-12 21:59:01 +00:00
maggesandClaude Sonnet 5	2b79411b68	Replace vendored docker-compose with podman-compose ... podman-compose and docker-compose aren't discovered the same way by `podman compose` - verified live (a fake-binary test reading podman's own provider-search error output) that docker-compose is searched for by exact path across a fixed list of CLI-plugin directories, while podman-compose is instead looked up as a plain command on $PATH. This package installs to /usr/local/bin/podman-compose accordingly, not under any cli-plugins/ directory. Unlike docker-compose (a single static Go binary), podman-compose is a Python script with two runtime dependencies neither of which ship with Unraid's own Python3 - PyYAML and python-dotenv, vendored here as plain pure-Python source (no C extension build; PyYAML's own fallback handles its optional C accelerator being absent). Verified end-to-end on a real host: with the previous docker-compose binary temporarily moved aside to confirm podman-compose was actually the one invoked, `podman compose up/ps/down` ran a real compose project correctly, including a live HTTP check against the started service. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-12 18:35:38 +00:00
maggesandClaude Sonnet 5	5b47b4cc0a	Add catatonit/nftables/docker-compose packages, fix CSRF/streaming/storage bugs found by live testing ... - Package #9-11: catatonit (pod infra init), nftables (netavark firewall backend), docker-compose (external compose provider for `podman compose`) — all vendored prebuilt binaries, versions.env pinned, propagated through build-packages.sh/release.sh/podman.plg/verify+update-packages.sh. - Fix WebUI: every POST action was silently failing (empty response body) because Unraid's own CSRF protection was never satisfied — app.js now sends the page's csrf_token as X-CSRF-Token. - Fix WebUI: PodmanClient::pullImage() assumed a single JSON response, but /images/pull actually streams newline-delimited JSON — every successful pull was throwing "Expected a JSON object/array response". - Fix WebUI: compose.php's up/down status detection had the same single-JSON-vs-NDJSON bug for `podman compose ps`, plus stderr was corrupting the parse. - Add cache-busting (?v=<mtime>) to Podman.page's script/style tags so a redeployed JS/CSS fix isn't served stale from browser cache. - Add a reusable modal dialog (app.js openFormModal) replacing prompt()/alert() for New Volume/Network/Pull Image. - Add host-path (bind-mount) support when creating a named volume. - Add Create Container (image, name, network mode incl. custom networks, ports, volumes, env, restart policy, privileged, start-after-create), auto-pulling the image on first use since /containers/create doesn't. All fixes verified live against a real podman system service and, where reachable, via the actual WebUI over the real socket — not just unit-level. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-12 11:51:17 +00:00
maggesandClaude Sonnet 5	51b7262b72	Fix five real bugs found by actually installing and running the plugin ... First live end-to-end install on real Unraid hardware (all 8 built packages installed via upgradepkg, rc.podman started, containers pulled/run/networked/port-mapped) — surfaced five genuine bugs no amount of container-based CI testing could have caught, since none of them exist inside the vbatts/slackware:15.0 build container: 1. rc.podman never created $PODMAN_LOG_DIR before redirecting the podman system service's output into it, so the service failed to even start ("No such file or directory"). Added it alongside the existing PODMAN_RUN_DIR mkdir. 2. config/storage.conf hardcoded a [storage] table, and podman-config.sh's `sync` step appended a second one at boot with the real graphroot/runroot — TOML forbids defining the same table twice. Removed the template's [storage] entirely; sync already generates the whole thing. 3. config/policy.json had a "_comment" pseudo-field for documentation, but containers/image's policy parser rejects any unknown top-level key outright. JSON has no comment syntax; moved the rationale into docs/ARCHITECTURE.md instead. 4. netavark >= 2.0 dropped its iptables firewall driver entirely (verified: passing "iptables" is flatly rejected) — nftables or firewalld are the only remaining options, and firewalld needs systemd/dbus, which Unraid has neither of. Set firewall_driver = "nftables" explicitly and documented that Unraid OS doesn't ship the `nft` binary this needs (a slackware64 nftables package works; not yet wired into the build/install pipeline — see follow-up). 5. Every container failed with "crun: pivot_root: Invalid argument". Root cause: Unraid's / is permanently the kernel's initial "rootfs" pseudo-filesystem (Unraid never pivots to a real one at boot — the whole OS runs from RAM), and pivot_root(2) unconditionally rejects that as the old root. This is not new: Docker/runc hits the exact same kernel restriction on this exact host and silently falls back to an MS_MOVE-based chroot; crun has no such fallback, only a --no-pivot flag with no config-file equivalent. Added plugin/sbin/crun-no-pivot.sh, a thin wrapper that scans crun's full argument list (podman puts global flags before the subcommand, so the subcommand isn't reliably $1) and injects --no-pivot right after create/run, and pointed containers.conf's crun runtime at it. Also fixed the podman.plg postinstall's chmod glob (`podman-*.sh` -> `*.sh`), which would have skipped this new non-podman-prefixed sbin script. Verified end-to-end on the real host: pull, run, real network connectivity (wget through the container's bridge), and a published port actually serving HTTP (curl through -p 8099:80 to nginx) all work. --no-pivot's security tradeoff (disabling one particular container-escape mitigation) was explicitly discussed with and approved by the user before committing, given it must be the default for any container to start at all on this platform. Follow-up not yet done: nftables (needed for #4) is not yet a packages/ component in the reproducible build pipeline — it was only installed manually on the test host for this verification run. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-11 23:06:53 +00:00
maggesandClaude Sonnet 5	e2fefcdf9c	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