The Moby Project ================ Moby is an open-source project created by Docker to enable and accelerate software containerization. It provides a "Lego set" of toolkit components, the framework for assembling…
The Moby Project
================

!GitHub License



Moby is an open-source project created by Docker to enable and accelerate software containerization.
It provides a "Lego set" of toolkit components, the framework for assembling them into custom container-based systems, and a place for all container enthusiasts and professionals to experiment and exchange ideas.
Components include container build tools, a container registry, orchestration tools, a runtime and more, and these can be used as building blocks in conjunction with other tools and projects.
Principles
Moby is an open project guided by strong principles, aiming to be modular, flexible and without too strong an opinion on user experience.
It is open to the community to help set its direction.
- Modular: the project includes lots of components that have well-defined functions and APIs that work together.
- Batteries included but swappable: Moby includes enough components to build fully featured container systems, but its modular architecture ensures that most of the components can be swapped by different implementations.
- Usable security: Moby provides secure defaults without compromising usability.
- Developer focused: The APIs are intended to be functional and useful to build powerful tools.
Audience
The Moby Project is intended for engineers, integrators and enthusiasts looking to modify, hack, fix, experiment, invent and build systems based on containers.
It is not for people looking for a commercially supported system, but for people who want to work and learn with open source code.
Relationship with Docker
The components and tools in the Moby Project are initially the open source components that Docker and the community have built for the Docker Project.
New projects can be added if they fit with the community goals. Docker is committed to using Moby as the upstream for the Docker Product.
However, other projects are also encouraged to use Moby as an upstream, and to reuse the components in diverse ways, and all these uses will be treated in the same way. External maintainers and contributors are welcomed.
The Moby project is not intended as a location for support or feature requests for Docker products, but as a place for contributors to work on open source code, fix bugs, and make the code more useful.
The releases are supported by the maintainers, community and users, on a best efforts basis only. For customers who want enterprise or commercial support, Docker Desktop and Mirantis Container Runtime are the appropriate products for these use cases.
Go modules
> [!IMPORTANT]
> Starting with Docker v29 (released November 2025), the Go module github.com/docker/docker is deprecated and won't be updated.
The supported public Go modules are:
| Module | Description |
|---|---|
| [github.com/moby/moby/client](client/) | Go client for the Docker Engine API |
| [github.com/moby/moby/api](api/) | API types shared between client and server |
The root module github.com/moby/moby/v2 is the codebase for building container engines based on Moby (such as Docker Engine).
It produces binaries only - it is not intended to be imported as a Go library and has no API stability guarantees.
Release tags
Docker Engine releases are tagged with a docker- prefix (e.g. docker-v29.0.0 for Docker Engine 29.0.0).
These tags are only used to build the Docker Engine binary from the root module - they must not be consumed via go get.
The client and api modules are versioned independently with their own tags (e.g. client/v1.x.x, api/v1.x.x).
Migrating from github.com/docker/docker
Replace the old import paths:
diff
- import "github.com/docker/docker/client"
+ import "github.com/moby/moby/client"
- import "github.com/docker/docker/api/types"
+ import "github.com/moby/moby/api/types"
Note that v29 includes many breaking API changes (option structs, renamed methods, moved types).
See the v29.0.0 release notes for the full list of Go SDK changes.
-----
Legal
=====
*Brought to you courtesy of our legal counsel. For more context,
please see the NOTICE document in this repo.*
Use and transfer of Moby may be subject to certain restrictions by the
United States and other governments.
It is your responsibility to ensure that your use and/or transfer does not
violate applicable laws.
For more information, please see https://www.bis.doc.gov
Licensing
=========
Moby is licensed under the Apache License, Version 2.0. See
LICENSE for the full
license text.
Members
-
moby ★ PINNED
The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
Go ★ 72k 2d agoExplain → -
buildkit ★ PINNED
concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
Go ★ 10k 21h agoExplain → -
swarmkit ★ PINNED
A toolkit for orchestrating distributed systems at any scale. It includes primitives for node discovery, raft-based consensus, task scheduling and more.
Go ★ 3.6k 1mo agoExplain → -
sys ★ PINNED
No description.
Go ★ 98 2d agoExplain → -
hyperkit
A toolkit for embedding hypervisor capabilities in your application
C ★ 3.7k 3y agoExplain → -
libnetwork
networking for containers
Go ★ 2.2k 2y agoExplain → -
vpnkit
A toolkit for embedding VPN capabilities in your application
OCaml ★ 1.2k 1mo agoExplain → -
datakit ▣
Connect processes into powerful data pipelines with a simple git-like filesystem interface
OCaml ★ 1.1k 2y agoExplain → -
spdystream
No description.
Go ★ 149 3mo agoExplain → -
docker-ci-zap
No description.
Go ★ 121 5y agoExplain → -
ipvs
IPVS networking for containers (package derived from moby/libnetwork)
Go ★ 110 2y agoExplain → -
tool ▣
Temporary repository for the moby assembly tool used by the Moby project
Go ★ 74 7y agoExplain → -
term
No description.
Go ★ 70 3mo agoExplain → -
libentitlement ▣
Entitlements library for high level control of container permissions
Go ★ 66 8y agoExplain → -
mobywebsite
website for the moby project
HTML ★ 34 2y agoExplain → -
qemu ⑂
Docker QEMU mirror with not yet upstreamed patches
C ★ 26 6y agoExplain → -
tsc
Moby Technical Steering Committee
★ 24 6y agoExplain → -
containerd
This is a limited-use, moby-specific, temporary "fork" of containerd -- not the (active) upstream containerd project!
Go ★ 23 3y agoExplain → -
locker
This is a direct pull from https://github.com/moby/moby/tree/master/pkg/locker
Go ★ 21 1y agoExplain → -
patternmatcher
No description.
Go ★ 21 3mo agoExplain → -
docker-image-spec
Docker Image Specification v1
Go ★ 20 2y agoExplain → -
docker-signal
Utility for signalling a docker daemon running on Windows to dump its stacks in the case of a deadlock
Go ★ 16 6y agoExplain → -
pubsub
No description.
Go ★ 13 3y agoExplain → -
profiles
A collection of security profiles for containers, including AppArmor and seccomp profiles used by Moby.
Go ★ 11 16d agoExplain → -
busybox
Dockerfile for a Windows busybox image
Dockerfile ★ 10 2y agoExplain → -
go-archive
Utility for packing and unpacking container tar archives
Go ★ 9 3d agoExplain → -
buildkit-bench
Set of benchmarks for BuildKit
Go ★ 4 2d agoExplain → -
datakit.logs ▣
CI state for DataKit CI
★ 4 6y agoExplain → -
policy-helpers
No description.
Go ★ 3 1mo agoExplain → -
docker-tdmgcc
TDM-GCC x64 Windows compilers for Docker CI
★ 3 10y agoExplain → -
go-swagger ⑂
Swagger 2.0 implementation for go
★ 3 6y agoExplain → -
flaky-ci-reports
https://moby.github.io/flaky-ci-reports/
HTML ★ 1 17d agoExplain → -
octoguard ▣
Reusable GitHub Actions workflows for security scanning, auditing, and compliance
★ 1 1y agoExplain →
No repos match these filters.