macOS
Homebrew已验证 · 100%
brew install buildkitlocal Homebrew formula metadata
安装
其他安装命令
Linux
Alpine Linux apk已验证 · 92%
sudo apk add buildkitAlpine Linux edge package indexes · buildkit · 来源: dl-cdn.alpinelinux.org
Nix已验证 · 92%
nix profile install nixpkgs#buildkitnixpkgs package indexes · pkgs/by-name/bu/buildkit/package.nix · 来源: api.github.com
Arch Linux pacman已验证 · 92%
sudo pacman -S buildkitArch Linux sync databases · buildkit · 来源: geo.mirror.pkgbuild.com
openSUSE zypper已验证 · 92%
sudo zypper install buildkitopenSUSE Tumbleweed package metadata · buildkit · 来源: download.opensuse.org
Windows
Scoop已验证 · 92%
scoop install main/buildkitScoop official bucket manifest trees · bucket/buildkit.json · 来源: api.github.com
概览
软件包摘要
Concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
历史
项目历史与用法
BuildKit is the Moby/Docker-era build backend that turned container image building into a reusable, cache-aware build toolkit rather than a Dockerfile-only code path. Its public identity centers on `buildctl`, `buildkitd`, LLB build graphs, pluggable frontends, cache import/export, and OCI/containerd-oriented workers.
项目历史
The project came out of a 2017 Moby proposal to separate the `docker build` experience into a reusable backend and allow different frontends to compile build descriptions into a lower-level build graph. The public `moby/buildkit` repository was created on 2017-05-31 and describes BuildKit as a toolkit for converting source code to build artifacts efficiently, expressively, and repeatably.
BuildKit's README presents LLB as the core intermediate representation and explicitly frames it as a Dockerfile-independent build graph format. That architectural split is the historical reason BuildKit became useful outside classic Dockerfiles: Dockerfile syntax is one frontend, but other projects can generate LLB directly or through their own frontend.
采用历史
BuildKit first became visible to Docker users through opt-in Docker builds, commonly via `DOCKER_BUILDKIT=1 docker build`, and then through Docker Buildx. The README now notes that `docker build` uses Buildx and BuildKit by default since Docker Engine 23.0, making BuildKit part of the ordinary Docker build path rather than only an experimental backend.
The upstream README lists Moby & Docker, Docker Buildx, Tekton Pipelines, Dagger, Earthly, Gitpod, Depot, Namespace, and other projects as users, showing how BuildKit moved from Docker internals into a broader cloud-native build substrate.
使用方式
As a standalone package, BuildKit is usually used as the `buildctl` client speaking to a `buildkitd` daemon. Users build Dockerfiles, export images or OCI artifacts, import and export caches, run rootless builds, or expose BuildKit as a service for CI and distributed builder setups.
For package-manager users, the appeal is that the same engine behind modern Docker builds can be installed separately, scripted directly, and connected to non-Docker runtimes or remote build workers.
为什么软件包爱好者会关心
BuildKit matters because it made Docker builds less linear and less Dockerfile-bound: concurrent dependency resolution, content-addressed cache behavior, cache exporters, and frontends gave package and CI people a much sharper tool for reproducible image construction.
It is also one of the clearer examples of a major container tool escaping its original CLI: the Homebrew formula gives macOS users `buildctl`, while the daemon normally lives on Linux or in a VM such as Lima.
时间线
- 2017: Moby BuildKit proposal and public `moby/buildkit` repository appear.
- 2018: Moby/Docker integration makes BuildKit available to Docker users through opt-in build paths.
- 2023: Docker Engine 23.0 makes Docker builds use Buildx and BuildKit by default.
- 2026: The upstream repository remains active and BuildKit is broadly used by container build systems.
Related projects
- BuildKit is closely related to `buildkitd`, `buildctl`, Docker Buildx, Moby/Docker, Dockerfile frontends, containerd, OCI image tooling, Tekton, Dagger, and Earthly.
来源
安全态势
尚未找到受保护工具覆盖
没有找到 buildkit 的匹配本地密钥处理 manifest。软件包元数据仍在此发布，以便未来覆盖拥有稳定的软件包 URL。
安装行为
- formula 元数据中未记录 Homebrew post-install 钩子。
- Homebrew bottle 元数据适用于 5 个平台目标。
- 构建元数据列出 1 个构建依赖。
建议审查
在无人值守的代理使用前，请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Linux
/etc/buildkit/buildkitd.toml~/.config/buildkit/buildkitd.toml
Credential files
Credential-bearing paths to review before unattended agent runs.
- Unix
$DOCKER_CONFIG/config.json~/.docker/config.json
可执行文件
已安装的可执行文件
| 命令 | 类型 | 暴露范围 | 备注 |
|---|---|---|---|
buildctl | cli | 全局可执行文件 |
新鲜度
版本和新鲜度
这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时，才会提示版本落后。
页面生成时间2026-11-04
管理器版本0.34.1
管理器更新时间2026-11-03
本地数据OK
上游当前
检测到的最新版本v0.34.2
https://github.com/moby/buildkit
- OK没有生成新鲜度警告。
安装元数据
软件包元数据
| 软件包键 | brew:buildkit |
|---|---|
| 版本 | 0.34.1 |
| 软件包管理器 | Homebrew |
| 软件包管理器页面 | https://formulae.brew.sh/formula/buildkit |
| 主页 | https://github.com/moby/buildkit |
| 仓库 | https://github.com/moby/buildkit |
| 许可证 | Apache-2.0 |
| 源码归档 | https://github.com/moby/buildkit/archive/refs/tags/v0.34.2.tar.gz |
| 最后更新 | 2026-11-03T14:13:19Z |
| Pulse | updated |
| 构建依赖 | go |
| Bottle | 可用 (于 arm64_golden_gate, arm64_linux, arm64_sequoia, arm64_tahoe, x86_64_linux) |
| Homebrew post-install | 未定义 |
| 服务 | 未声明 |
注册表事实
源数据库详情
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | buildkit |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
源数据库匹配
其他软件包管理器记录
匹配项来自外部软件包管理器索引，并与本地 Automic Vault 软件包链接分开显示。
Nix95%
buildkit
nix profile install nixpkgs#buildkit- normalized package name match
- 匹配方式：Buildkit
apk95%
buildctl 0.32.2-r0
Concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit (cli frontend)
https://github.com/moby/buildkit
sudo apk add buildctl- License: Apache-2.0
- Architecture: x86_64
- Source Package: buildkit
- 1 依赖
- 1 提供
- normalized package name match
- 匹配方式：Buildkit
apk95%
buildkit 0.32.2-r0
Concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
https://github.com/moby/buildkit
sudo apk add buildkit- License: Apache-2.0
- Architecture: x86_64
- Source Package: buildkit
- 1 依赖
- 1 提供
- normalized package name match
- 匹配方式：Buildkit
apk95%
buildkit-doc 0.32.2-r0
Concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit (documentation)
https://github.com/moby/buildkit
sudo apk add buildkit-doc- License: Apache-2.0
- Architecture: x86_64
- Source Package: buildkit
- normalized package name match
- 匹配方式：Buildkit
apk95%
buildkit-openrc 0.32.2-r0
Concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit (OpenRC init scripts)
https://github.com/moby/buildkit
sudo apk add buildkit-openrc- License: Apache-2.0
- Architecture: x86_64
- Source Package: buildkit
- normalized package name match
- 匹配方式：Buildkit
pacman95%
buildkit 0.32.2-1
A toolkit for converting source code to build artifacts in a repeatable manner
https://github.com/moby/buildkit
sudo pacman -S buildkit- License: Apache-2.0
- Architecture: x86_64
- 2 依赖
- 1 可选依赖
- normalized package name match
- 匹配方式：Buildkit
zypper95%
buildkit 0.32.2-1.1
Toolkit for converting source code to build artifacts
https://github.com/moby/buildkit
sudo zypper install buildkit- License: Apache-2.0
- Category: Unspecified
- Architecture: x86_64
- Source Package: buildkit
- 4 依赖
- 1 提供
- normalized package name match
- 匹配方式：Buildkit
Scoop95%
main/buildkit
scoop install main/buildkit- normalized package name match
- 匹配方式：Buildkit
来源线索
由仓库数据生成
此页面由 av-web 从 scripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。
Combined YAML source
View the package source record on GitHub.
使用的来源
- Geiger risk classifier
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- external package-manager database matches
- package relationship graph
- package version freshness
- package-page enrichment
- pkg.so package database
- pkgdb category and tag curation