From 3ceb534c1bee32da96ea2070af5a3db9a85b5265 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Wed, 22 Nov 2017 17:55:37 +0100 Subject: [PATCH] Fix PortBindings definition in Swagger Signed-off-by: Sebastiaan van Stijn Upstream-commit: a50cf8aa44f2a5abb5900d39008d075d2e8c2850 Component: engine --- components/engine/api/swagger.yaml | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/components/engine/api/swagger.yaml b/components/engine/api/swagger.yaml index a6b5ee5cfd..c276a52cd6 100644 --- a/components/engine/api/swagger.yaml +++ b/components/engine/api/swagger.yaml @@ -606,17 +606,7 @@ definitions: description: "Network mode to use for this container. Supported standard values are: `bridge`, `host`, `none`, and `container:`. Any other value is taken as a custom network's name to which this container should connect to." PortBindings: - type: "object" - description: "A map of exposed container ports and the host port they should map to." - additionalProperties: - type: "object" - properties: - HostIp: - type: "string" - description: "The host IP address" - HostPort: - type: "string" - description: "The host port number, as a string" + $ref: "#/definitions/PortMap" RestartPolicy: $ref: "#/definitions/RestartPolicy" AutoRemove: