BuildKit
6.8#2 in container enginesFree planFree planAPILinuxmacOSSelf-hosted
VisitBuildKit vs gVisor
What both publish
| Fact | BuildKit | gVisor |
|---|---|---|
| Architecture | BuildKit is composed of the buildkitd daemon and the buildctl client. | A sandbox includes a Sentry application kernel that handles system calls and a Gofer process that mediates filesystem access. |
| Purpose | BuildKit converts source code into build artifacts efficiently and repeatably. | gVisor is an open-source Linux-compatible sandbox and application kernel that isolates containers from the host operating system. |
| Security reporting | Security issues should be reported privately to [email protected], and the project currently does not offer a paid security bounty program. | The project asks that sensitive security reports be sent to its security mailing list or submitted privately through GitHub advisories, and says a response is typically provided within 48 hours. |
| Support | The README directs users to the #buildkit channel on Docker Community Slack. | The project directs users to GitHub issues, documentation, and mailing lists for support and community discussion. |
BuildKit plans
- BuildKit (Apache License 2.0)Free
gVisor plans
- gVisorFree
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 gVisor if…
gVisor suits teams running untrusted container workloads on supported Linux hosts, particularly those using Docker or Kubernetes. It may also suit users who need container checkpointing or trace-point output for an external detection engine.