Guillaume LoursandPaweł Gronowski
333776c7cf
Add the lifecycle core of the jobs extension. Registration is idempotent on a canonical spec hash, so formatting and defaults do not change a job's identity, and a spec from a newer contract fails validation on an older daemon. Create-and-run fires the first run before anything else can reach the new job. Container specs with a negative StopTimeout are rejected, as runs must be stoppable, and so is the host-dependent Local timezone. Every fire goes through one chokepoint serialized per job, which applies the concurrency policy and persists the run record before the container is created, so a crash always leaves a discoverable run. A fire is detached from its caller, as the daemon completes a container start even when the request goes away. A run whose start is unknown, because the start request failed or its record could not be written, has its container stopped and keeps the job occupied until the container exits. Outcomes are persisted before auto-removal, and failed terminal or idle writes are retried instead of leaving the job stuck; only the job's latest run returns it to idle. Cancels and timeouts always stop the container, even after the other decided the outcome, so a failed stop is not final. The scheduler is one goroutine over a min-heap, dispatching through the same chokepoint. On start, missed occurrences follow the missed-fires policy with at most one catch-up, and an occurrence moved by a reschedule is kept. A reschedule replaces exactly one occurrence, including one a tick already consumed but has not fired yet. A dispatched fire is dropped if its job was paused, resumed or removed since, and the next-fire time is persisted from the scheduler's current state after the fire is recorded, so a delayed fire cannot undo a newer change and a crash cannot lose the occurrence. A fire deferred by the queue policy keeps its occurrence recorded until it runs, so a restart in between catches it up. Removing a job keeps its run history by default, reachable by the removed job's ID, and run containers are removed with their records. Stored specs are compared as the running daemon canonicalizes them, so jobs survive upgrades that change the container API types. Co-authored-by: Paweł Gronowski <pawel.gronowski@docker.com> Signed-off-by: Guillaume Lours <glours@users.noreply.github.com> Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.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.