maggesandClaude Sonnet 5
2b79411b68
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>
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).