BuildKit
6.8#2 in container enginesFree planFree planAPILinuxmacOSSelf-hosted
VisitBuildKit vs runc
What both publish
| Fact | BuildKit | runc |
|---|---|---|
| Build features | Features include concurrent dependency resolution, instruction caching, cache import and export, multiple output formats, and automatic garbage collection. | Build tags include seccomp syscall filtering, libpathrs path safety, and an option to disable checkpoint and restore. |
| Integrations | The repository lists Moby and Docker, Tekton Pipelines, Docker buildx, Gitpod, Dagger, and other projects as BuildKit users. | The project documents using runc with Docker to prepare a root filesystem and with systemd or other process supervisors to manage containers. |
| License | The repository identifies its license as Apache-2.0. | The code and documentation are released under the Apache 2.0 license. |
| Purpose | BuildKit converts source code into build artifacts efficiently and repeatably. | runc is a command-line tool for spawning and running containers on Linux according to the OCI specification. |
| Security reporting | Security issues should be reported privately to [email protected], and the project currently does not offer a paid security bounty program. | The OCI security policy directs vulnerability reports to [email protected] rather than GitHub issues or pull requests. |
BuildKit plans
- BuildKit (Apache License 2.0)Free
runc plans
No prices published.
Pick BuildKit if…
BuildKit suits developers and teams who need configurable, cache-aware builds and multiple artifact formats. It also fits users who want rootless execution or integration with Docker and other listed projects.
Pick runc if…
You want what its maker publishes above — check its page for the details.