maggesandClaude Sonnet 5
c3b8ae8ed9
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>
packages/
One subdirectory per Slackware .txz package required by the plugin, built
against Unraid's Slackware base. See
docs/ARCHITECTURE.md, section 5
for the full rationale (why these components, static linking preference,
version pinning, build strategy).
Packages
| Directory | Upstream project | Purpose |
|---|---|---|
podman/ |
containers/podman | Core container engine binary |
conmon/ |
containers/conmon | Container monitor process |
crun/ |
containers/crun | OCI runtime (preferred over runc) |
netavark/ |
containers/netavark | Network backend |
aardvark-dns/ |
containers/aardvark-dns | DNS for container-to-container name resolution |
containers-common/ |
containers/common | Default config/seccomp/registries templates |
fuse-overlayfs/ |
containers/fuse-overlayfs | Fallback storage driver (rootless, Phase 2) |
passt/ |
passt.top (no GitHub mirror) | Rootless networking (Phase 2), successor to slirp4netns |
unraid-podman/ |
this repository (not an upstream project) | Plugin's own scaffolding — rc.podman, sbin/ scripts, event/ hooks, config templates (see its README) |
podman, conmon, crun, netavark, aardvark-dns, passt,
fuse-overlayfs, and unraid-podman are built and released automatically by
.github/workflows/build-packages.yml. containers-common currently only
supplies reference config (see config/) and is not yet wired
into the automated build.
Standard layout per package
Each package directory follows the same skeleton:
packages/<name>/
├── <name>.SlackBuild # Slackware build script (source download, build, packaging)
├── slack-desc # Slackware package description (max 70 cols / 11 lines)
├── patches/ # Optional patches applied during the build
└── README.md # Upstream version pinned, build notes, patch rationale
Build pipeline
Packages are built via scripts/build-packages.sh, which runs each
package's <name>.SlackBuild in turn (see scripts/lib/slackbuild-common.sh
for the shared fetch/verify/package helpers they all use). This must run
inside a Slackware-compatible build environment — never on an arbitrary host
distro, to avoid glibc/ABI drift against Unraid's base.
.github/workflows/build-packages.yml is the CI entry point: it runs the
same script inside a pinned Slackware container
(scripts/ci/setup-slackware-buildenv.sh bootstraps any build-time
dependency the base image doesn't already ship) and uploads the results as a
workflow artifact — nothing built is ever committed to this repository.
Exact upstream versions and source checksums are pinned centrally in
versions.env (update via scripts/update-versions.sh,
never by hand) and, at release time, mirrored into the top-level
plugin/podman.plg manifest together with MD5 checksums by
scripts/release.sh, so installs are reproducible and rollback-able — see
docs/ARCHITECTURE.md, section 14 (Rollback).