the versioned api docs have the same indentation errors as
swagger.yaml. spec compliant parsers like js-yaml or libfyaml fail to
parse all of them.
flow collections that span lines are converted from flow style to
block style. continuation lines of multi-line double-quoted strings
are indented deeper than their key. the parsed data does not change.
Signed-off-by: Florian Stellbrink <flo@stellbr.ink>
The `UnpackedSize` field was added in 050afe1e1a,
which originally had it as a top-level field, but later moved it to
`Size.Unpacked`.
This caused issues with current (v3.6) versions of go-swagger, which added
validation for this;
2026/09/22 12:33:56 reading config from /go/src/github.com/moby/moby/api/swagger-gen.yaml
2026/09/22 12:33:56 validating spec /go/src/github.com/moby/moby/api/swagger.yaml
The swagger spec at "/go/src/github.com/moby/moby/api/swagger.yaml" is invalid against the swagger specification 2.0. See errors :
- "UnpackedSize" is present in required but not defined as property in schema "ImageManifestSummary.ImageData"
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Keep the archived Swagger specifications consistent with the current
API specification and the Go struct field name.
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Add HostConfig.Umask and pass it to the OCI process spec for container
entrypoints, exec processes, and healthchecks.
Preserve the configured umask when exec user resolution reconstructs the
OCI User value, so runtimes receive it in the per-exec process spec.
Keep the field aligned with OCI's uint32 representation - raw JSON
clients need to use 18 for octal 0022 for example.
Co-authored-by: Youfu Zhang <zhangyoufu@gmail.com>
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Add support for filtering containers by annotation on
GET /containers/json, similar to the existing label filter:
`annotation=key` matches containers carrying the annotation key,
and `annotation=key=value` also matches its value.
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
The POST /build resource query parameters are declared as bare
integers, which code generators commonly map to 32-bit values. The
daemon parses these parameters as signed 64-bit integers.
Add the int64 format to the affected versioned API documents so
generated clients can represent valid resource limits above i32::MAX.
Signed-off-by: Niel Drummond <niel@drummond.lu>
Update older versions of the API docs with the changes made in
37302166e0 (api: document
Task.NetworksAttachments in the swagger definition) and
99c1a9c778 (daemon: Add
configurable default container stop timeout).
For older API versions I slightly adjusted the wording for the
timeout to not mention `default-stop-timeout`, because that option
is not present on older daemons, so I kept it to "daemon defaults".
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
ContainerUpdate only starts applying per-device blkio settings in the
current API version.
The fields existed in the Go request type before that because it shares
`container.Resources` with other endpoints, but they were not documented
as supported for container update and older daemons ignored them.
Clear these fields when handling requests for older API versions so
clients pinned to those versions keep the previous behavior, while v1.55
clients can use the newly supported fields.
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Both query parameters are now collectionFormat: multi arrays in the
swagger so they can accept multiple values later without an API
version bump. The server still operates on a single platform and
rejects requests passing more than one; type is read directly as a
list of repeated values instead of a comma-separated string.
Signed-off-by: Sopho Merkviladze <smerkviladze@mirantis.com>
Add a new Engine API endpoint that returns the in-toto attestation
statements attached to an image for a given platform. The endpoint
locates the attestation manifest(s) referencing the requested platform's
image manifest, enumerates the statement layers, and returns each
layer's OCI descriptor (including media type, digest, size, and
annotations) together with its in-toto predicate type.
Query parameters:
- platform: JSON-encoded OCI platform; defaults to the daemon's host
platform if omitted.
- type: comma-separated list of in-toto predicate type URIs; if
omitted, all statements are returned.
- statement: boolean, defaults to false. When true, the daemon reads
each matching statement blob and includes the verbatim in-toto JSON
in the response. When false (or omitted), statement blobs are not
read and the Statement field is absent from each entry.
The manifest-chain walk (locating the platform image manifest and its
associated attestation manifest) is delegated to policy-helpers'
image.ResolveSignatureChain so that moby and BuildKit agree on how to
interpret the attestation storage format. The statement-layer iteration
and blob reading is inlined: when statement bodies are requested it
fails fast on the first unreadable blob and reads matching blobs
eagerly into memory; otherwise statement-layer blobs are never read
from the content store.
The endpoint is implemented for the containerd image store. The legacy
graphdriver store returns errdefs.NotImplemented (HTTP 501).
Signed-off-by: Sopho Merkviladze <smerkviladze@mirantis.com>
Syncs changes from 2ecaac9631
and d5f6bdb027 to older API
versions, in addition to formatting changes.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Document that /swarm/join requires ListenAddr, RemoteAddrs, and JoinToken in the Engine API spec.
ListenAddr is already required by join validation, while a non-empty listen address without a port uses the default swarm listening port. This keeps the API docs aligned with current behavior without changing swarm runtime behavior.
Fixes#49159
Signed-off-by: Ashutosh Anand <ashutoshanand2560@gmail.com>
Follow-up to ca69153e28 and
0d2d3f348d, which restored old API docs.
This patch aligns the formatting of older versions with the format we use now.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Apply the same Topology schema fix as api/swagger.yaml to v1.42–v1.54
document snapshots so clients generating from pinned API versions see the
correct Segments map shape.
Signed-off-by: Nishant Maheshwari <mnishant222@gmail.com>
Made-with: Cursor
This parameter was added in 59169d0f97
(API v1.49, docker 28.5.1), but forgot to update the swagger definition.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Florian Stellbrink