docker/build-push-action
5,314 stars·722 forks·TypeScript·Apache-2.0·13 viewsgithub.com/marketplace/actions/build-and-push-docker-images↗
Build Push Action
This project is a GitHub Action that automates the building and pushing of Docker container images to OCI registries. It functions as a multi-platform container builder and publisher using the Buildx engine to create images compatible with multiple hardware architectures.
The tool distinguishes itself through software supply chain security features, including the generation of software bills of materials and provenance attestations to verify image integrity. It optimizes construction speed via remote cache management and supports secure secret injection to prevent sensitive data from persisting in image layers.
The capability surface covers build context configuration, including the resolution of source code via Git URIs, and a metadata-driven tagging system for applying labels and version tags. It also provides execution summaries and statistics to audit build job results.
Features
- Multi-Architecture Images - Provides a comprehensive system for building and bundling container images for multiple CPU architectures and operating systems.
- Automated Image Build Pipelines - Automates the end-to-end process of building multi-platform images and pushing them to OCI registries.
- BuildKit-Based Builds - Utilizes the BuildKit engine via Buildx to perform efficient, concurrent container image construction.
- Cross-Platform Build Targets - Enables the specification of multiple hardware architectures as target platforms for the build process.
- OCI Container Registry Clients - Implements an automated process for uploading container images to OCI-compliant registries with custom tagging.
- Docker Image Builds - Automates the build and push cycle of Docker images as a core part of the CI pipeline.
- Docker Container Deployments - Integrates the image creation process into GitHub Actions to ensure images are ready for deployment.
- Multi-Platform Builds - Generates container images targeting multiple hardware architectures and operating systems for broad device compatibility.
- SBOM Attestation Generation - Generates verifiable software bills of materials and provenance attestations for supply chain security.
- Software Supply Chain Security - Secures the software supply chain by generating SBOMs and provenance attestations for container images.
- Remote Cache Management - Accelerates build times by fetching and exporting layer caches to an external registry.
- Build Configurations - Allows the definition of build-time variables, labels, and target stages to control image construction.
- Build Context Resolution - Allows source code to be fetched directly from Git URIs to serve as the build context.
- Remote Build Caches - Accelerates builds by exporting and importing layer caches via external OCI registries.
- Build Context Injectors - Manages the inclusion of local files and remote Git references within the container build context.
- Build Configuration - Provides configuration settings to define how source files and build modes are handled.
- Build Cache Optimizations - Optimizes image construction speed through remote caching and specialized build-time mounts.
- Container Image Tagging - Implements a metadata-driven system for applying version tags and labels to the resulting container images.
- Secret Injection Mechanisms - Injects sensitive credentials into the build process using temporary mounts to prevent secrets from persisting in image layers.
- Secret Mounts - Injects sensitive credentials into the build process using ephemeral mounts to keep them out of image layers.
- Container Image Metadata - Attaches custom labels, version tags, and provenance records to the resulting container images.
- Software Bill of Materials Generators - Automatically generates comprehensive software bills of materials and inventories of components during the build process.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
