# apko mit Homebrew, apk, Nix, pacman, zypper installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für apko in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:apko ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install apko ``` Evidenz: local Homebrew formula metadata ### Linux - apk (92%): ```sh sudo apk add apko ``` Evidenz: Alpine Linux edge package indexes: apko from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz - Nix (92%): ```sh nix profile install nixpkgs#apko ``` Evidenz: nixpkgs package indexes: pkgs/by-name/ap/apko/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman (92%): ```sh sudo pacman -S apko ``` Evidenz: Arch Linux sync databases: apko from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz - zypper (92%): ```sh sudo zypper install apko ``` Evidenz: openSUSE Tumbleweed package metadata: apko from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst ## Paketfakten - **Paketschlüssel:** brew:apko - **Paketmanager:** Homebrew - **Paketmanager-Seite:** - **Version:** 1.2.23 - **Quellzusammenfassung:** Build OCI images from APK packages directly without Dockerfile - **Homepage:** - **Repository:** - **Upstream-Dokumentation:** - **Lizenz:** Apache-2.0 - **Quellarchiv:** - **Zuletzt aktualisiert:** 2026-07-07T15:33:11Z - **Generiert:** 2026-07-08T07:18:31+00:00 ## Executables - apko (cli) - apko (Alias) ## Build-Abhängigkeiten - go ## Installationsverhalten - Post-install-Hook: nicht definiert - Bottle: verfügbar auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Version und Aktualität - Seite generiert: 2026-07-08 - Manager-Version: 1.2.23 - Manager aktualisiert: 2026-07-07 - lokale Daten: OK - Upstream-Repository: https://github.com/chainguard-dev/apko - neueste erkannte Version: v1.2.23 (aktuell) ## Projektgeschichte und Nutzung apko is Chainguard's apk-based OCI image builder: it builds container images directly from APK package repositories and a declarative YAML file, without Dockerfiles or RUN steps. It belongs to the supply-chain-focused family of tools that treat packages, SBOMs, and reproducibility as first-class image-build inputs. ### Projektgeschichte The public repository was created in February 2022. The README says apko was created by Chainguard because they needed secure, reproducible container images for their tooling, with speed important because images are rebuilt constantly for new versions and patches. The design is explicitly declarative. Official docs state that apko files are YAML definitions of an image and that, unlike Dockerfiles, there is no equivalent of RUN statements. That restriction lets apko make stronger claims about image contents and reproducibility and generate metadata such as SBOMs. apko is paired with melange, Chainguard's tool for building APK packages from source. The README frames melange plus apko as covering most use cases: package software into APKs with melange, then assemble minimal OCI images from those packages with apko. ### Adoptionsgeschichte The README documents Homebrew installation, go install from source, and use of the cgr.dev/chainguard/apko container image. The supplied package metadata also records packaging in Alpine apk, Homebrew, Nix, pacman, and zypper, which fits a tool aimed at distro and container-package workflows. GitHub repository metadata showed over 1.6k stars and an active release stream. The latest official release assets include signed binaries and checksums, reflecting packaging practices expected in supply-chain-oriented infrastructure tools. ### Wie es verwendet wird A typical apko file specifies APK repositories and packages under contents, then image metadata such as entrypoint, command, environment, accounts, paths, architectures, annotations, and layering. apko build writes a tar image, while apko publish pushes directly to a registry. There is no fixed user config file location in the official docs; users pass an apko YAML file path to the CLI. The file can include another local file or a file from a remote git repository. ### Warum Paket-Nerds sich dafür interessieren apko is important to package nerds because it moves image construction from shell-script layers to package-manager inputs. Instead of a Dockerfile mutating a filesystem, an image is a closure over APK repositories, package names, keys, accounts, paths, and metadata. For distroless-style images, SBOM generation, rebuild speed, and bit-for-bit reproducibility, apko is a concrete example of packaging discipline influencing container image tooling. ### Zeitleiste - 2022: Public chainguard-dev/apko repository created on GitHub. - 2022: README quickstart already showed apk-package-based Alpine image builds and SBOM generation. - 2022: Companion melange repository was created for building APK packages from source. - 2026: Official release stream reached the v1.2.x series with signed multi-platform binaries. ### Related projects - The README names melange as apko's sister tool for producing APK packages, and says apko's design is influenced by ko and distroless. It also points to kontain.me as related declarative image-building work. ### Quellen - - - - - - source_facts.package-manager ## Sicherheitshinweise Für apko wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat. ## Details aus der Quelldatenbank - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** apko - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Andere Paketmanager-Einträge - Nix - apko: normalized package name match | nixpkgs package indexes: pkgs/by-name/ap/apko/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - apk - apko - 0.9.0-r25: normalized package name match | Alpine Linux edge package indexes: apko from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | declarative APK-based container building tool with support for Sigstore signatures | https://github.com/chainguard-dev/apko - apk - apko-bash-completion - 0.9.0-r25: normalized package name match | Alpine Linux edge package indexes: apko-bash-completion from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Bash completions for apko | https://github.com/chainguard-dev/apko - apk - apko-fish-completion - 0.9.0-r25: normalized package name match | Alpine Linux edge package indexes: apko-fish-completion from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Fish completions for apko | https://github.com/chainguard-dev/apko - apk - apko-zsh-completion - 0.9.0-r25: normalized package name match | Alpine Linux edge package indexes: apko-zsh-completion from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Zsh completions for apko | https://github.com/chainguard-dev/apko - pacman - apko - 1.2.15-1: normalized package name match | Arch Linux sync databases: apko from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Declarative APK-based container building tool with support for sigstore signatures | https://github.com/chainguard-dev/apko - zypper - apko - 1.2.16-1.1: normalized package name match | openSUSE Tumbleweed package metadata: apko from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst | Build OCI images from APK packages directly without Dockerfile | https://github.com/chainguard-dev/apko - zypper - apko-bash-completion - 1.2.16-1.1: normalized package name match | openSUSE Tumbleweed package metadata: apko-bash-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst | Bash Completion for apko | https://github.com/chainguard-dev/apko - zypper - apko-fish-completion - 1.2.16-1.1: normalized package name match | openSUSE Tumbleweed package metadata: apko-fish-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst | Fish Completion for apko | https://github.com/chainguard-dev/apko - zypper - apko-zsh-completion - 1.2.16-1.1: normalized package name match | openSUSE Tumbleweed package metadata: apko-zsh-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst | Zsh Completion for apko | https://github.com/chainguard-dev/apko ## Verwandte Links - [Cloud CLI packages](https://www.automicvault.com/de/pkg/cloud-clis/) - Belongs to a cloud or infrastructure command family. - [Source-control packages](https://www.automicvault.com/de/pkg/source-control-tools/) - Belongs to a source-control command family. - [Terminal utility packages](https://www.automicvault.com/de/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Developer build packages](https://www.automicvault.com/de/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [go](https://www.automicvault.com/de/pkg/brew/go/) - Build dependency declared by Homebrew. - [skopeo](https://www.automicvault.com/de/pkg/brew/skopeo/) - Shares av.db curated category or tags: cli, cloud-infrastructure, images, oci. - [container](https://www.automicvault.com/de/pkg/brew/container/) - Shares av.db curated category or tags: cli, cloud-infrastructure, oci. - [containerd](https://www.automicvault.com/de/pkg/brew/containerd/) - Shares av.db curated category or tags: cli, cloud-infrastructure, oci. - [dcp](https://www.automicvault.com/de/pkg/brew/dcp/) - Shares av.db curated category or tags: cli, cloud-infrastructure, oci. - [oci-cli](https://www.automicvault.com/de/pkg/brew/oci-cli/) - Shares av.db curated category or tags: cli, cloud-infrastructure, oci. - [oras](https://www.automicvault.com/de/pkg/brew/oras/) - Shares av.db curated category or tags: cli, cloud-infrastructure, oci. - [rockcraft](https://www.automicvault.com/de/pkg/brew/rockcraft/) - Shares av.db curated category or tags: cli, cloud-infrastructure, oci. - [timoni](https://www.automicvault.com/de/pkg/brew/timoni/) - Shares av.db curated category or tags: cli, cloud-infrastructure, oci. - [crane](https://www.automicvault.com/de/pkg/brew/crane/) - Local package facts share a topical domain. Shared terms: cli, cloud, cloud-infrastructure, images, infrastructure. - [crossplane](https://www.automicvault.com/de/pkg/brew/crossplane/) - Local metadata places this package in an adjacent workflow. Shared terms: build, cli, cloud, cloud-infrastructure, infrastructure. ## Combined YAML source View the package source record on GitHub. [combined/apko.yml](https://github.com/automic-vault/db/blob/main/combined/apko.yml) ## Quellen - Nucleus package database - Geiger risk classifier - package-page enrichment - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph