aboutsummaryrefslogtreecommitdiff
path: root/vendor/github.com/docker/docker/api/swagger.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'vendor/github.com/docker/docker/api/swagger.yaml')
-rw-r--r--vendor/github.com/docker/docker/api/swagger.yaml174
1 files changed, 119 insertions, 55 deletions
diff --git a/vendor/github.com/docker/docker/api/swagger.yaml b/vendor/github.com/docker/docker/api/swagger.yaml
index 8652c368c..38ca5329e 100644
--- a/vendor/github.com/docker/docker/api/swagger.yaml
+++ b/vendor/github.com/docker/docker/api/swagger.yaml
@@ -19,10 +19,10 @@ produces:
consumes:
- "application/json"
- "text/plain"
-basePath: "/v1.40"
+basePath: "/v1.41"
info:
title: "Docker Engine API"
- version: "1.40"
+ version: "1.41"
x-logo:
url: "https://docs.docker.com/images/logo-docker-main.png"
description: |
@@ -49,8 +49,8 @@ info:
the URL is not supported by the daemon, a HTTP `400 Bad Request` error message
is returned.
- If you omit the version-prefix, the current version of the API (v1.40) is used.
- For example, calling `/info` is the same as calling `/v1.40/info`. Using the
+ If you omit the version-prefix, the current version of the API (v1.41) is used.
+ For example, calling `/info` is the same as calling `/v1.41/info`. Using the
API without a version-prefix is deprecated and will be removed in a future release.
Engine releases in the near future should support this version of the API,
@@ -210,6 +210,43 @@ definitions:
PathInContainer: "/dev/deviceName"
CgroupPermissions: "mrw"
+ DeviceRequest:
+ type: "object"
+ description: "A request for devices to be sent to device drivers"
+ properties:
+ Driver:
+ type: "string"
+ example: "nvidia"
+ Count:
+ type: "integer"
+ example: -1
+ DeviceIDs:
+ type: "array"
+ items:
+ type: "string"
+ example:
+ - "0"
+ - "1"
+ - "GPU-fef8089b-4820-abfc-e83e-94318197576e"
+ Capabilities:
+ description: |
+ A list of capabilities; an OR list of AND lists of capabilities.
+ type: "array"
+ items:
+ type: "array"
+ items:
+ type: "string"
+ example:
+ # gpu AND nvidia AND compute
+ - ["gpu", "nvidia", "compute"]
+ Options:
+ description: |
+ Driver-specific options, specified as a key/value pairs. These options
+ are passed directly to the driver.
+ type: "object"
+ additionalProperties:
+ type: "string"
+
ThrottleDevice:
type: "object"
properties:
@@ -421,10 +458,11 @@ definitions:
items:
type: "string"
example: "c 13:* rwm"
- DiskQuota:
- description: "Disk limit (in bytes)."
- type: "integer"
- format: "int64"
+ DeviceRequests:
+ description: "a list of requests for devices to be sent to device drivers"
+ type: "array"
+ items:
+ $ref: "#/definitions/DeviceRequest"
KernelMemory:
description: "Kernel memory limit in bytes."
type: "integer"
@@ -665,6 +703,19 @@ definitions:
description: "A list of kernel capabilities to drop from the container. Conflicts with option 'Capabilities'"
items:
type: "string"
+ CgroupnsMode:
+ type: "string"
+ enum:
+ - "private"
+ - "host"
+ description: |
+ cgroup namespace mode for the container. Possible values are:
+
+ - `"private"`: the container runs in its own private cgroup namespace
+ - `"host"`: use the host system's cgroup namespace
+
+ If not specified, the daemon default is used, which can either be `"private"`
+ or `"host"`, depending on daemon version, kernel support and configuration.
Dns:
type: "array"
description: "A list of DNS servers for the container to use."
@@ -1103,6 +1154,7 @@ definitions:
type: "object"
additionalProperties:
type: "array"
+ x-nullable: true
items:
$ref: "#/definitions/PortBinding"
example:
@@ -1127,7 +1179,6 @@ definitions:
PortBinding represents a binding between a host IP address and a host
port.
type: "object"
- x-nullable: true
properties:
HostIp:
description: "Host IP address that the container's port is mapped to."
@@ -2831,6 +2882,18 @@ definitions:
type: "object"
additionalProperties:
type: "string"
+ # This option is not used by Windows containers
+ Capabilities:
+ type: "array"
+ description: |
+ A list of kernel capabilities to be available for container (this overrides the default set).
+ items:
+ type: "string"
+ example:
+ - "CAP_NET_RAW"
+ - "CAP_SYS_ADMIN"
+ - "CAP_SYS_CHROOT"
+ - "CAP_SYSLOG"
NetworkAttachmentSpec:
description: |
Read-only spec type for non-swarm containers attached to swarm overlay
@@ -3767,7 +3830,7 @@ definitions:
description: |
The driver to use for managing cgroups.
type: "string"
- enum: ["cgroupfs", "systemd"]
+ enum: ["cgroupfs", "systemd", "none"]
default: "cgroupfs"
example: "cgroupfs"
NEventsListener:
@@ -3789,6 +3852,17 @@ definitions:
or "Windows Server 2016 Datacenter"
type: "string"
example: "Alpine Linux v3.5"
+ OSVersion:
+ description: |
+ Version of the host's operating system
+
+ <p><br /></p>
+
+ > **Note**: The information returned in this field, including its
+ > very existence, and the formatting of values, should not be considered
+ > stable, and may change without notice.
+ type: "string"
+ example: "16.04"
OSType:
description: |
Generic type of the operating system of the host, as returned by the
@@ -4002,7 +4076,7 @@ definitions:
SecurityOptions:
description: |
List of security features that are enabled on the daemon, such as
- apparmor, seccomp, SELinux, and user-namespaces (userns).
+ apparmor, seccomp, SELinux, user-namespaces (userns), and rootless.
Additional configuration options for each security feature may
be present, and are included as a comma-separated list of key/value
@@ -4015,6 +4089,7 @@ definitions:
- "name=seccomp,profile=default"
- "name=selinux"
- "name=userns"
+ - "name=rootless"
ProductLicense:
description: |
Reports a summary of the product license on the daemon.
@@ -4569,9 +4644,9 @@ paths:
parameters:
- name: "name"
in: "query"
- description: "Assign the specified name to the container. Must match `/?[a-zA-Z0-9_-]+`."
+ description: "Assign the specified name to the container. Must match `/?[a-zA-Z0-9][a-zA-Z0-9_.-]+`."
type: "string"
- pattern: "/?[a-zA-Z0-9_-]+"
+ pattern: "^/?[a-zA-Z0-9][a-zA-Z0-9_.-]+$"
- name: "body"
in: "body"
description: "Container to create"
@@ -5135,15 +5210,15 @@ paths:
Note: This endpoint works only for containers with the `json-file` or `journald` logging driver.
operationId: "ContainerLogs"
responses:
- 101:
- description: "logs returned as a stream"
- schema:
- type: "string"
- format: "binary"
200:
- description: "logs returned as a string in response body"
+ description: |
+ logs returned as a stream in response body.
+ For the stream format, [see the documentation for the attach endpoint](#operation/ContainerAttach).
+ Note that unlike the attach endpoint, the logs endpoint does not upgrade the connection and does not
+ set Content-Type.
schema:
type: "string"
+ format: "binary"
404:
description: "no such container"
schema:
@@ -5163,10 +5238,7 @@ paths:
type: "string"
- name: "follow"
in: "query"
- description: |
- Return the logs as a stream.
-
- This will return a `101` HTTP response with a `Connection: upgrade` header, then hijack the HTTP connection to send raw output. For more information about hijacking and the stream format, [see the documentation for the attach endpoint](#operation/ContainerAttach).
+ description: "Keep connection after returning logs."
type: "boolean"
default: false
- name: "stdout"
@@ -5427,7 +5499,7 @@ paths:
/containers/{id}/resize:
post:
summary: "Resize a container TTY"
- description: "Resize the TTY for a container. You must restart the container for the resize to take effect."
+ description: "Resize the TTY for a container."
operationId: "ContainerResize"
consumes:
- "application/octet-stream"
@@ -6181,12 +6253,17 @@ paths:
in: "query"
description: "If “1”, “true”, or “True” then it will be an error if unpacking the given content would cause an existing directory to be replaced with a non-directory and vice versa."
type: "string"
+ - name: "copyUIDGID"
+ in: "query"
+ description: "If “1”, “true”, then it will copy UID/GID maps to the dest file or dir"
+ type: "string"
- name: "inputStream"
in: "body"
required: true
description: "The input stream must be a tar archive compressed with one of the following algorithms: identity (no compression), gzip, bzip2, xz."
schema:
type: "string"
+ format: "binary"
tags: ["Container"]
/containers/prune:
post:
@@ -6459,6 +6536,11 @@ paths:
description: "Target build stage"
type: "string"
default: ""
+ - name: "outputs"
+ in: "query"
+ description: "BuildKit output configuration"
+ type: "string"
+ default: ""
responses:
200:
description: "no error"
@@ -9066,7 +9148,9 @@ paths:
type: "string"
RemoteAddrs:
description: "Addresses of manager nodes already participating in the swarm."
- type: "string"
+ type: "array"
+ items:
+ type: "string"
JoinToken:
description: "Secret token for joining this swarm."
type: "string"
@@ -9522,23 +9606,16 @@ paths:
get:
summary: "Get service logs"
description: |
- Get `stdout` and `stderr` logs from a service.
+ Get `stdout` and `stderr` logs from a service. See also [`/containers/{id}/logs`](#operation/ContainerLogs).
- **Note**: This endpoint works only for services with the `json-file` or `journald` logging drivers.
+ **Note**: This endpoint works only for services with the `local`, `json-file` or `journald` logging drivers.
operationId: "ServiceLogs"
- produces:
- - "application/vnd.docker.raw-stream"
- - "application/json"
responses:
- 101:
- description: "logs returned as a stream"
- schema:
- type: "string"
- format: "binary"
200:
- description: "logs returned as a string in response body"
+ description: "logs returned as a stream in response body"
schema:
type: "string"
+ format: "binary"
404:
description: "no such service"
schema:
@@ -9567,10 +9644,7 @@ paths:
default: false
- name: "follow"
in: "query"
- description: |
- Return the logs as a stream.
-
- This will return a `101` HTTP response with a `Connection: upgrade` header, then hijack the HTTP connection to send raw output. For more information about hijacking and the stream format, [see the documentation for the attach endpoint](#operation/ContainerAttach).
+ description: "Keep connection after returning logs."
type: "boolean"
default: false
- name: "stdout"
@@ -9779,23 +9853,16 @@ paths:
get:
summary: "Get task logs"
description: |
- Get `stdout` and `stderr` logs from a task.
+ Get `stdout` and `stderr` logs from a task. See also [`/containers/{id}/logs`](#operation/ContainerLogs).
- **Note**: This endpoint works only for services with the `json-file` or `journald` logging drivers.
+ **Note**: This endpoint works only for services with the `local`, `json-file` or `journald` logging drivers.
operationId: "TaskLogs"
- produces:
- - "application/vnd.docker.raw-stream"
- - "application/json"
responses:
- 101:
- description: "logs returned as a stream"
- schema:
- type: "string"
- format: "binary"
200:
- description: "logs returned as a string in response body"
+ description: "logs returned as a stream in response body"
schema:
type: "string"
+ format: "binary"
404:
description: "no such task"
schema:
@@ -9824,10 +9891,7 @@ paths:
default: false
- name: "follow"
in: "query"
- description: |
- Return the logs as a stream.
-
- This will return a `101` HTTP response with a `Connection: upgrade` header, then hijack the HTTP connection to send raw output. For more information about hijacking and the stream format, [see the documentation for the attach endpoint](#operation/ContainerAttach).
+ description: "Keep connection after returning logs."
type: "boolean"
default: false
- name: "stdout"