Cory Snider
eeec2b0531
The skip can go: the rejoin latch behind the flake is fixed earlier in this branch, and the departed incarnation which used to linger in the books went with the work this is stacked on. What is left is a closing check which counts rather than names -- every node had to hold exactly five active nodes and no failed ones -- and neither count is an invariant. A node which starts after another has departed can still be told of that departed incarnation by gossip already in flight, where it sits in failedNodes until something supersedes it at its address, so which nodes carry such a straggler is a matter of timing. Nor does a count of five ever say that the five are the ones which ought to be there. Assert what reconverging means instead: every node sees all five of the current nodes as active, by ID rather than by count. That is what the relaunched three cannot bring about for themselves, since they do no join, and it is indifferent to whatever stragglers a node picked up on the way. The rejoin fault this test has always been aimed at still shows, as a node which never appears. Both checks are clean on this base -- 80 runs of the counting one, 60 of this one -- so the rewrite buys robustness rather than fixing a failure in front of us. Assisted-by: Claude Opus 5 Signed-off-by: Cory Snider <csnider@mirantis.com>
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 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. They are not necessarily intended as end user tools but as components aimed at developers. Documentation and UX is aimed at developers not end users.
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/dockeris deprecated and won't be updated.
The supported public Go modules are:
| Module | Description |
|---|---|
github.com/moby/moby/client |
Go client for the Docker Engine API |
github.com/moby/moby/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:
- 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.