Build Container
Build Container is a reusable GitHub Actions workflow for building container images and bundles from source using Docker BuildKit.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
68/100 Good
- Maintained
- 100last commit 16 days ago
- Popular
- 3991 GitHub stars
- Easy to install
- 400 install platforms, install notes, setup guide, Docker image
- Light to run
- 304 GB minimum RAM
- Security check
- 95no serious findings, CI, tests
- GitHub stars
- 91
- Open issues
- 20
- Last commit
- 2026-11-05
- Latest release
- v1.19.0
- License
- Apache-2.0
- Activity
- steady
Checked 15 days ago - source: GitHub (docker/github-builder)
Resources & Compatibility
Minimum requirements: 4 GB RAM, 6 GB disk. ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Set your real project and image names Before starting, replace the sample ${PROJECT_ID}, repository, and image values in the build config with your own. Without these, the build won't know where to put the finished container. source
- Put code in the /workspace folder When using a custom builder, the source is placed in /workspace, the folder the builder uses as its working directory. If files or your Dockerfile are not where the build expects them, the container build can fail. source
- Push the image if you need it later Add a docker push step after the build step if you want to store the container in your registry (the place you keep container images). Without it, the image only exists during the build and can't be pulled later. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What does Docker do to a build container after a Dockerfile RUN command finishes?
A build container is created for Dockerfile instructions such as RUN, where the command is run and the container is committed to an image layer.
What must be replaced in a build config before building the container image?
Set your real project and image names by replacing the sample project, repository, and image values. Without these, the build will not know where to put the finished container.
Where must the source code be placed when using a custom builder?
Put the code in the /workspace folder because the builder uses that folder as its working directory. If files or the Dockerfile are not where the build expects them, the container build can fail.
How can a self-hosted build agent container be extended with additional tools?
You can create a basic build agent and extend the Dockerfile to include additional tools and their dependencies. You can also build your own container by using that agent image as a base layer.
Answers sourced from docs.cloud.google.com, docs.cloud.google.com, forums.docker.com, www.reddit.com
Community
- FAQ - Linux Containers Forum (forum)
- Non-Wordpress self hosted website builders alternative to ... - Reddit (reddit)
- What is a "build container" - Docker Community Forums (forum)
- Categories - Linux Containers Forum (forum)
- Looking for a Open Source / Self hosted Website Builder to ... - Reddit (reddit)
Collected 48 days ago - public community threads