Installer manifest-tool avec Homebrew, apk, dnf, Nix

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• manifest-tool

Historique du projet

The public repository was created in March 2016. The README describes manifest-tool as one of the first command-line tools capable of assembling Docker v2.2 manifest lists, later more commonly known as OCI image indexes.

The project's history section says the codebase began as a joint project with Harshal Patil from IBM Bangalore and was originally forked from registry client code in skopeo, which later became part of the Red Hat container tooling ecosystem. The v2 rewrite removed the original skopeo-derived code, while the old code remained part of v1 releases.

Historique d'adoption

manifest-tool gained relevance during the transition from one-image-per-architecture publishing to a single image reference that can resolve to architecture-specific images. The README notes that Docker's early `docker manifest` command was based on code from manifest-tool through a Docker CLI pull request in early 2018.

The project distributes release binaries for many architectures and also publishes a Docker image, matching the multi-platform audience it serves. By 2026 the repository had hundreds of stars and forks, indicating continued use even after Docker and other container tools added overlapping functionality.

Modes d'utilisation

Users inspect an image reference with `manifest-tool inspect` to see manifest or index entries and platform support. For publishing, `manifest-tool push` can read a YAML spec or command-line arguments that list platforms, source image templates, target image references, and tags.

For pushing to a registry, the README says credentials can be supplied on the command line, via credential helper support similar to the Docker client, or through an existing Docker client configuration.

Pourquoi les passionnés de paquets s'y intéressent

For package and container infrastructure maintainers, manifest-tool is historically important because it represents the period when multi-arch container images were still being assembled with specialized external tooling. It is also a useful reference point for the evolution from Docker manifest lists to OCI indexes.

Chronologie

• 2016: Public GitHub repository created.
• 2016: Docker v2.2 manifest lists were the target format described by the project.
• 2018: Docker CLI manifest work drew on manifest-tool code according to the README.
• 2025: v2.2.0 release published.
• 2026: v2.2.2 release published.

Related projects

• The README names skopeo as the original registry-client lineage for early manifest-tool code.
• The README points to `mquery` as a related utility for querying public image references.
• The Docker CLI `docker manifest` command is described by the README as having incorporated much of manifest-tool's original functionality.

Sources

• https://github.com/docker/cli/pull/138
• https://github.com/estesp/manifest-tool
• https://github.com/estesp/manifest-tool#readme
• https://github.com/estesp/manifest-tool/releases/tag/v2.2.2
• https://github.com/estesp/mquery