docker/build-push-action — a developer tool — sits at 5.4k GitHub stars in the Developer Tools space. GitHub Action to build and push Docker images with Buildx
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
GitHub Action to build and push Docker images with Buildx
with full support of the features provided by Moby BuildKit
builder toolkit. This includes multi-platform build, secrets, remote cache, etc.
and different builder deployment/namespacing options.
Usage
Git context
Path context
Examples
Summaries
Customizing
inputs
outputs
environment variables
Troubleshooting
Contributing
Usage
In the examples below we are also using 3 other actions:
setup-buildx action will
create and boot a builder using by default the docker-container driver.
This is not required but recommended using it to be able to build
multi-platform images, export cache, etc.
setup-qemu action can be
useful if you want to add emulation support with QEMU to be able to build
against more platforms.
login action will take care to
log in against a Docker registry.
Git context
By default, this action uses the Git context,
so you don't need to use the actions/checkout
action to check out the repository as this will be done directly by BuildKit.
The git reference will be based on the event that triggered your workflow
and will result in the following context: https://github.com/<owner>/<repo>.git#<ref>.
name: ci
on:
push:
jobs:
docker:
runs-on: ubuntu-latest
steps:
-
name: Login to Docker Hub
uses: docker/login-action@v4
with:
username: ${{ vars.DOCKERHUB_USERNAME }}
password: ${{ secrets.DOCKERHUB_TOKEN }}
-
name: Set up QEMU
uses: docker/setup-qemu-action@v4
-
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v4
-
name: Build and push
uses: docker/build-push-action@v7
with:
push: true
tags: user/app:latest
Be careful because any file mutation in the steps that precede the build step
will be ignored, including processing of the .dockerignore file since
the context is based on the Git reference. However, you can use the
Path context using the context input alongside
the actions/checkout action to remove
this restriction.
Default Git context can also be provided using the Handlebars template
expression {{defaultContext}}. Here we can use it to provide a subdirectory
to the default Git context:
Building from the current repository automatically uses the GitHub Token,
so it does not need to be passed. If you want to authenticate against another
private repository, you have to use a secret
named GIT_AUTH_TOKEN to be able to authenticate against it with Buildx:
name: ci
on:
push:
jobs:
docker:
runs-on: ubuntu-latest
steps:
-
name: Checkout
uses: actions/checkout@v6
-
name: Login to Docker Hub
uses: docker/login-action@v4
with:
username: ${{ vars.DOCKERHUB_USERNAME }}
password: ${{ secrets.DOCKERHUB_TOKEN }}
-
name: Set up QEMU
uses: docker/setup-qemu-action@v4
-
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v4
-
name: Build and push
uses: docker/build-push-action@v7
with:
context: .
push: true
tags: user/app:latest
Examples
Multi-platform image
Secrets
Push to multi-registries
Manage tags and labels
Cache management
Export to Docker
Test before push
Validating build configuration
Local registry
Share built image between jobs
Named contexts
Copy image between registries
Update Docker Hub repo description
SBOM and provenance attestations
Annotations
Reproducible builds
Summaries
This action generates a job summary
that provides a detailed overview of the build execution. The summary shows an
overview of all the steps executed during the build, including the build inputs
and eventual errors.
The summary also includes a link for downloading the build record with
additional details about the build, including build stats, logs, outputs, and
more. The build record can be imported to Docker Desktop for inspecting the
build in greater detail.
[!WARNING]
If you're using the actions/download-artifact
action in your workflow, you need to ignore the build record artifacts
if name and pattern inputs are not specified (defaults to download all artifacts of the workflow),
otherwise the action will fail:
How active is development on docker/build-push-action?
The most recent commit recorded on docker/build-push-action was 3 months ago, based on the GitHub push timestamp. The repository has 735 forks — one of the better signals of community interest.
How many stars does docker/build-push-action have?
docker/build-push-action has 5.4k GitHub stars — refresh the page for the live number, or check github.com/docker/build-push-action. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is docker/build-push-action open source?
Yes — docker/build-push-action ships under the Apache-2.0 license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/docker/build-push-action.
What else is in the Developer Tools space?
docker/build-push-action is tracked by TopGit under the Developer Tools category, alongside 5 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What is docker/build-push-action?
docker/build-push-action (docker/build-push-action) is a TypeScript project on GitHub. From the project's own README: GitHub Action to build and push Docker images with Buildx
What language is docker/build-push-action written in?
docker/build-push-action is written primarily in TypeScript. GitHub's language field is based on the largest share of bytes in the default branch.
What license does docker/build-push-action use?
docker/build-push-action is released under the Apache-2.0 license. Always verify the LICENSE file directly on GitHub for the authoritative terms — license strings can be edited out of sync with a project's actual stance.
Where do I read more about docker/build-push-action?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/docker/build-push-action is the definitive source.
Read full README in the tab above.
Curious whether build-push-action is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about build-push-action.