HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
moby
buildkit
Go2018–2025
moby / buildkit

buildkit

concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit

30Distinct people
36Mentions
0Explicit recommenders
10.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:59:52 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year36 dated mentions

Observed mentions: 2018-04-16 21:09:07 UTC to 2025-12-24 23:32:32 UTC.

02468102018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC514
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC514
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC909
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC817
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC404

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
BuildKit BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Key features: Automatic garbage collection Extendable frontend formats Concurrent dependency resolution Efficient instruction caching Build cache import/export Nested build job invocations Distributable workers Multiple output formats Pluggable architecture Execution without root privileges Read the proposal from moby/moby#32925 Introductory blog post https://blog.mobyproject.org/introducing-buildkit-17e056cc5317 Join #buildkit channel on Docker Community Slack NoteIf you are visiting this repo for the usage of BuildKit-only Dockerfile features like RUN --mount=type=(bind|cache|tmpfs|secret|ssh), please refer to the Dockerfile reference. Notedocker build uses Buildx and BuildKit by default since Docker Engine 23.0. You don't need to read this document unless you want to use the full-featured standalone version of BuildKit. Used by Quick start Linux Setup Windows Setup macOS Setup Build from source Exploring LLB Frontends Exploring Dockerfiles Building a Dockerfile with buildctl Building a Dockerfile using external frontend Output Image/Registry Local directory Docker tarball OCI tarball containerd image store Cache Garbage collection Export cache Inline (push image and cache together) Registry (push image and cache separately) Local directory GitHub Actions cache (experimental) S3 cache (experimental) Azure Blob Storage cache (experimental) Consistent hashing Metadata Systemd socket activation Expose BuildKit as a TCP service Load balancing Containerizing BuildKit Podman Nerdctl Kubernetes Daemonless OpenTelemetry support Running BuildKit without root privileges Building multi-platform images Configuring buildctl Color Output Controls Number of log lines (for active steps in tty mode) Contributing Used by BuildKit is used by the following projects: Moby & Docker (DOCKER_BUILDKIT=1 docker build) img OpenFaaS Cloud container build interface Tekton Pipelines (formerly Knative Build Templates) the Sanic build tool vab Rio kim PouchContainer Docker buildx Okteto Cloud Earthly earthfiles Gitpod Dagger envd Depot Namespace Unikraft DevZero dacc Quick start ℹ️ For Kubernetes deployments, see examples/kubernetes. BuildKit is composed of the buildkitd daemon and the buildctl client. While the buildctl client is available for Linux, macOS, and Windows, the buildkitd daemon is only available for Linux and *Windows currently. The latest binaries of BuildKit are available here for Linux, macOS, and Windows. Linux Setup The buildkitd daemon requires the following components to be installed: runc or crun containerd (if you want to use containerd worker) Starting the buildkitd daemon: You need to run buildkitd as the root user on the host. $ sudo buildkitd To run buildkitd as a non-root user, see docs/rootless.md. The buildkitd daemon supports two worker backends: OCI (runc) and containerd. By default, the OCI (runc) worker is used. You can set --oci-worker=false --containerd-worker=true to use the containerd worker. We are open to adding more backends. To start the buildkitd daemon using systemd socket activation, you can install the buildkit systemd unit files. See Systemd socket activation The buildkitd daemon listens gRPC API on /run/buildkit/buildkitd.sock by default, but you can also use TCP sockets. See Expose BuildKit as a TCP service. Windows Setup See instructions and notes at docs/windows.md. macOS Setup Homebrew formula (unofficial) is available for macOS. $ brew install buildkit The Homebrew formula does not contain the daemon (buildkitd). For example, Lima can be used for launching the daemon inside a Linux VM. brew install lima limactl start template://buildkit export BUILDKIT_HOST="unix://$HOME/.lima/buildkit/sock/buildkitd.sock" Build from source To build BuildKit from source, see .github/CONTRIBUTING.md. For a buildctl reference, see this document. Exploring LLB BuildKit builds are based on a binary intermediate format called LLB that is used for defining the dependency graph for processes running part of your build. tl;dr: LLB is to Dockerfile what LLVM IR is to C. Marshaled as Protobuf messages Concurrently executable Efficiently cacheable Vendor-neutral (i.e. non-Dockerfile languages can be easily implemented) See solver/pb/ops.proto for the format definition, and see ./examples/README.md for example LLB applications. Frontends BuildKit supports different build languages through frontends that translate build definitions into LLB. The following frontends and tools provide alternatives for defining builds: Project Description Dockerfile Build container images using Dockerfile instructions. Buildpacks Build applications using buildpacks. Mockerfile Example YAML frontend for Ubuntu packages and external dependencies. Gockerfile Build simple Go servers from YAML definitions. bldr (Pkgfile) Build and package software distributions using YAML definitions. HLB Define builds as containerized units of work in a high-level build language. Earthfile (Earthly) Define repeatable builds with Dockerfile-like syntax. No longer actively maintained. Cargo Wharf (Rust) Build Rust container images from Cargo build plans with per-dependency caching. Nix Build container images from Nix derivations and flakes. mopy (Python) Package Python applications into container images using YAML definitions. envd (Starlark) Define container-based development environments for AI/ML. Blubber Build application container images from declarative YAML. Bass Script builds and project infrastructure with a Lisp dialect. kraft.yaml (Unikraft) Build Unikraft unikernel images from Kraftfiles. Massé Define composable container image build graphs in CUE. DALEC Build system packages and container images from declarative specifications. Dexfile Extend Dockerfile syntax with conditions, loops, imports, and functions. Doc
Read the full README on GitHub

What Hacker News says

5 sources
Use the experimental BuildKit Dockerfile frontend for much improved build time mounting: https://github.com/moby/buildkit/blob/master/frontend/docker... * You can mount build-time secrets in safely with `--mount-type=secret`, instead of passing them in. (Multistage builds do alleviate the problems with passing secrets in, but not completely.) * Buildkit automatically parallelizes build stages. (Of course!) * Mount apt-cache dirs in at build time with `--mount-type bind` so that you don't have to apt-get update every single time, and you don't have to clear apt-caches either. And lots more. Notice that this mostly involves capabilities that Docker already has to build time.
In Intro Guide to Dockerfile Best Practices
Here’s a little known fact: “docker build” can trivially be extended to build buildpacks or CNB. Now that the buildkit refactoring is complete, Dockerfiles are just the default frontend. There’s already a buildpack frontend in the community repo, and it works great. Writing your own frontend is real straightforward. Honestly after years of stagnation, the most exciting work on container building is now coming out of Docker. Buildkit is amazing, a real hidden gem. See https://github.com/moby/buildkit
In Defence Against the Docker Arts
I would say check out buildkit, which is the tech behind "docker build"'s new builder. I don't know if the Dockerfile format is really suitable for this, but you can now build your own format and Docker can just build it. Basically buldkit breaks things down into a frontend format (like Dockerfile) and a frontend parser which gets specified as an image at the top of your file (`#syntax=<some image>`), the parser converts the frontend format into an intermediary language (called llb), buildkit takes the llb and passes it to a backend worker. This all happens behind the scenes with `DOCKER_BUILDKIT=1 docker build -t myImage .` Docker actually ships new Dockerfile features that aren't tied to a docker version this way. Actually there are a number of new Dockerfile features that might get you what you need, even if the format isn't all that g
Read the rest
reat, at least it's relatively natural to reason about. Things like cache mounts, secrets, mounting (not copying) images into a build stage's "RUN" directive, lots of great stuff. This is all officially supported stuff. Here's a demo of "docker build" building from a buildpack spec instead of Dockerfile: https://github.com/tonistiigi/buildkit-pack - buildkit - https://github.com/moby/buildkit - official Docker docs - https://docs.docker.com/develop/develop-images/build_enhance... - buildkit Dockerfile docs - https://github.com/moby/buildkit/blob/master/frontend/docker...
In Goodbye Docker and Thanks for all the Fish

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.