Verified end-to-end with a full local build of all 8 packages on the
actual runner host (docker exec against vbatts/slackware:15.0, bind-
mounted repo on the cache pool) instead of round-tripping through
Gitea Actions for each fix — much faster for a chain of issues this
deep. All 8 packages now build successfully from a clean checkout.
Three fixes, all in crun (the last package still failing):
1. "Package requirements (json-c >= 0.14) were not met" — added
json-c to the toolchain bootstrap.
2. crun depends on the libocispec git submodule, which in turn depends
on the image-spec and runtime-spec git submodules. GitHub's source
archive tarball never includes submodule content (no .git directory
for `git submodule update` to work against — the existing `|| true`
masked this failing silently). Fetched all three as their own
pinned tarballs instead, at the exact commits crun 1.28 references
(cross-checked via the GitHub contents API), matching how every
other dependency in this project is already pinned.
3. crun.c unconditionally #includes git-version.h, which crun's own
Makefile only generates via `git describe` (again, no .git) or from
a pre-existing .tarball-git-version.h — the file crun's own `make
dist` would have written, which we never run. Write that file
ourselves in the exact format the Makefile already expects; this is
the documented fallback path bundled release tarballs rely on, not
a workaround around it.
Also includes the podman go-md2man pre-seed fix and setup-slackware-
buildenv.sh python3 addition from the previous commit's follow-up
testing (both already verified working in this same local build run).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- 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>
maggesandClaude Sonnet 5