Freedom251 › Container Build Tools
apko

What apko is
apko is a free, open-source command-line tool for building and publishing OCI container images from APK packages. Declarative YAML selects packages, architectures, and distributions, producing lightweight flat images intended to contain only application requirements. The project describes images as bitwise reproducible, and successful builds generate SBOM files. Builds are daemonless, and the CLI can publish completed images directly to a container registry. Configurations can target multiple architectures, but one build cannot mix Wolfi and Alpine packages. apko does not run arbitrary Dockerfile-style commands; custom software and shell commands must be supplied through APK packages, which the companion tool melange can produce. It supports the s6 supervision suite for multiple container processes, documents Docker usage, and provides a GitHub Actions build action. Installation options include Homebrew, mise, Go source installation, and the project’s container image. The README calls apko a work in progress. Linux, macOS, and self-hosted use are listed, with questions directed to the #apko channel on Kubernetes Slack.
Who it suits
apko suits developers who build minimal, reproducible OCI images from APK packages using declarative configuration. It fits workflows needing multi-architecture output, SBOM generation, or direct registry publishing.
What it does well
- Free and open source
- Bitwise-reproducible images
- SBOM files from successful builds
- Daemonless image builds
- Multi-architecture support
What to know first
- Cannot mix Wolfi and Alpine packages
- No arbitrary Dockerfile-style commands
- Custom software must be packaged as APK
- Project is described as work in progress
Verdict
apko offers a package-driven alternative to Dockerfile image construction, emphasizing small, reproducible outputs and SBOMs. Its declarative model requires software and shell steps to exist in APK packages first.
Facts from apko's own pages
- Build speed
- The project says apko aims to build images in milliseconds. · github.com, 4 Oct 2026
- Build step limit
- apko cannot run arbitrary Dockerfile-style build commands; software installation and shell commands must be included in APK packages. · edu.chainguard.dev, 4 Oct 2026
- Companion tool
- Chainguard identifies melange as a companion tool for producing APK packages to use with apko. · github.com, 4 Oct 2026
- Compatibility
- The README says apko can build from any environment with apk tooling and shows loading generated images into Docker. · github.com, 4 Oct 2026
- Declarative configuration
- apko files are declarative and do not support an equivalent of Dockerfile RUN statements. · github.com, 4 Oct 2026
- Image output
- It builds and publishes OCI container images composed from APK packages. · github.com, 4 Oct 2026
- Image publishing
- The CLI can publish a built image directly to a registry. · github.com, 4 Oct 2026
- Image size
- Generated images contain only what the application needs, in the style of distroless images. · github.com, 4 Oct 2026
- Installation
- The project README lists installation through Homebrew, mise, Go source installation, or its container image. · github.com, 4 Oct 2026
- Integrations
- The project documents use with Docker and provides an apko build action for GitHub Actions CI/CD pipelines. · edu.chainguard.dev, 4 Oct 2026
- Minimal images
- apko focuses on lightweight, flat base images containing selected packages. · edu.chainguard.dev, 4 Oct 2026
- Multi architecture
- An image configuration can specify architectures, and apko can compose images for different architectures and distributions. · edu.chainguard.dev, 4 Oct 2026
- Package ecosystem limit
- A single apko build cannot mix Wolfi and Alpine packages. · edu.chainguard.dev, 4 Oct 2026
- Package requirement
- Custom tools and applications must first be packaged as apk packages, which can be built with the sister tool melange. · github.com, 4 Oct 2026
- Project status
- The README describes apko as a work in progress and says details are subject to change. · github.com, 4 Oct 2026
- Publishing
- The CLI can publish generated images directly to a container registry. · github.com, 4 Oct 2026
- Purpose
- apko builds and publishes OCI container images from apk packages. · github.com, 4 Oct 2026
- Reproducibility
- The project says apko images are fully bitwise reproducible by design. · github.com, 4 Oct 2026
- SBOM
- apko produces a software bill of materials that details the packages inside an image. · github.com, 4 Oct 2026
- Security reporting
- The security policy asks users to report vulnerabilities by email and says reporters can expect acknowledgment within 72 hours. · github.com, 4 Oct 2026
- Services
- apko supports the s6 supervision suite to run multiple processes in a container. · github.com, 4 Oct 2026
- Support
- The project README directs users with questions to the #apko channel on Kubernetes Slack. · github.com, 4 Oct 2026
- What it does
- apko is an open-source command-line tool that builds container images from APK packages using declarative YAML configuration. · edu.chainguard.dev, 4 Oct 2026
Where apko stands on Freedom251
- Container Build Tools#9 of 34