package proto_docker

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message ContainerInfo

docker.proto:144

Used in: ListContainersResponse

message CreateContainerRequest

docker.proto:90

Used in: Request

message CreateContainerResponse

docker.proto:99

Used in: Response

message CreateVolumeRequest

docker.proto:180

Used in: Request

message CreateVolumeResponse

docker.proto:186

Used in: Response

message DeleteContainerRequest

docker.proto:130

Used in: Request

message DeleteContainerResponse

docker.proto:134

Used in: Response

message DeleteVolumeRequest

docker.proto:190

Used in: Request

message DeleteVolumeResponse

docker.proto:194

Used in: Response

message ExecuteCommandRequest

docker.proto:170

Used in: Request

message ExecuteCommandResponse

docker.proto:175

Used in: Response

message GetPortsRequest

docker.proto:155

Used in: Request

message GetPortsResponse

docker.proto:166

Used in: Response

message InspectContainerRequest

docker.proto:112

Used in: Request

message InspectContainerResponse

docker.proto:116

Used in: Response

message ListContainersRequest

docker.proto:141

This only lists the containers belonging to the Polypheny instance issuing the request. Ownership is determined by enforcing a naming scheme which includes the Polypheny UUID in the container name.

Used in: Request

(message has no fields)

message ListContainersResponse

docker.proto:150

Used in: Response

message PingRequest

docker.proto:198

Used in: Request

(message has no fields)

message PingResponse

docker.proto:201

Used in: Response

message PortBinding

docker.proto:13

See https://pkg.go.dev/github.com/docker/go-connections/nat#PortMap

Used in: PortMap

message PortMap

docker.proto:17

Used in: PortMaps

message PortMapOrError

docker.proto:159

Used in: GetPortsResponse

message PortMaps

docker.proto:22

Used in: CreateContainerRequest, PortMapOrError

message Request

docker.proto:35

In general we do not keep the strict protobuf field numbering policies, because we never store messages. The exception is the message_id, version and upgrade field numbers for both Request and Response are fixed, as are the VersionRequest, VersionResponse, UpgradeRequest and UpgradeResponse messages. All other fields can be changed if the version is increased.

message Response

docker.proto:54

message StartContainerRequest

docker.proto:104

Used in: Request

message StartContainerResponse

docker.proto:108

Used in: Response

message StopContainerRequest

docker.proto:122

Used in: Request

message StopContainerResponse

docker.proto:126

Used in: Response

message StringList

docker.proto:26

Used in: CreateContainerRequest, ExecuteCommandRequest

message UpgradeRequest

docker.proto:82

Used in: Request

message UpgradeResponse

docker.proto:86

Used in: Response

message VersionRequest

docker.proto:73

Used in: Request

message VersionResponse

docker.proto:77

Used in: Response