Push your code to GitHub and Zeabur deploys it, as on zeabur.com. Zeabur Builder is the part of Zeabur that turns a Git repository into an app that can run: it finds the language your code is in, builds it, and builds again when the branch changes.
You don't need to install anything from this repository.
- Zeabur Builder is a component from the Zeabur Catalog. Open Cluster → Components, find Zeabur Builder and click Install. When it's missing, the Add menu also lists it under Deploy from Git.
To deploy, open a project and select Add → Deploy from Git: Build and deploy a service from Git. The rest of Zeabur, from installing it on a server to running your services, is in the Zeabur documentation.
- Finds your language. With Railpack, it builds Node.js, Python, Go, PHP, Ruby, Java, Rust, Elixir, Deno, .NET, Gleam, C++ and Zig apps, static sites and shell scripts without a Dockerfile. If your repository has a Dockerfile, it builds that instead.
- Rebuilds when the branch changes. Push to the branch and a new version is built. With Zeabur and Keel, the service then switches to it.
- Keeps build secrets out of the image. Build variables, such as a token for private packages, reach the build as secrets, so they aren't stored in the image unless your build copies them there.
- Runs on your server. Builds and their cache stay on your own machines and your own registry.
Zeabur Builder also works without Zeabur. It is a Kubernetes operator that builds container images from Git with BuildKit and hands the digest to your rollout tool.
A Build names a Git repository and a builder:
apiVersion: builder.zeabur.com/v1alpha1
kind: Build
metadata: {name: whoami, namespace: team-a}
spec:
source: {type: git, git: {url: https://github.com/traefik/whoami}}
builderRef: dockerfileFor every new commit on the ref, the controller builds an image, pushes it to
<registry.host>/<namespace>/<name> and writes it to status.latestImage as
<repository>:<tag>@<digest>. Leave out ref to follow the repository's default branch;
status.resolvedRef says which branch that was.
- Two builders.
dockerfilebuilds your Dockerfile.railpackplans the build with Railpack for repositories without one; its images run as uid 1000, so they start under Pod Securityrestricted. - Tags rollout tools can sort.
main-1761058800-3e1a9c2(branch, Unix time, commit), one per build, newest last.spec.output.tagTemplateandextraTagschange them. - One buildkitd per namespace. Each namespace that builds gets its own buildkitd, cache,
certificate authority and registry path. The cache stays on buildkitd's volume between builds,
so
RUN --mount=type=cachekeeps its contents; it never goes to the registry. An idle buildkitd scales to zero after 10 minutes. - Build variables as secrets.
spec.envreaches the build as BuildKit secrets, from a value or a Secret key. - Uploaded folders.
spec.source.archivebuilds a folder that a client pushed to the registry as an OCI artifact, by digest (archive sources). - Small. One controller, a buildkitd per building namespace, one Job per build, three custom
resources. The Job runs
buildctland needs no privileges.
buildkitd runs privileged, inside a user namespace. Builds in one namespace trust each other, and
namespaces alone don't isolate code from people you don't trust: for that, run buildkitd in a
sandbox runtime with --buildkitd-runtime-class and on nodes of its own.
Security has the trust model.
Zeabur Builder builds images and stops there. Tests, deployment and log storage belong to your pipeline, rollout tool and log collector.
For Zeabur users:
Using Zeabur Builder on its own:
- Install and your first Build
- Triggers, private repositories, archive sources, rollout, external registries and build nodes
- Registry tokens, controller permissions and releases
- How it works and security
See CONTRIBUTING.md. Report security issues as described in SECURITY.md, which also describes the trust model.