Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
Used in:
Used in:
The UUID of the created container
Used in:
Must start with polypheny_ followed by the Polypheny UUID and another underscore
Used in:
Length > 0 when an error occurred
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Set when there was another error
Used in:
Used in:
Used in:
Used in:
Length > 0 when an error occurred
See https://docs.docker.com/engine/api/v1.43/#tag/Container/operation/ContainerInspect
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:
(message has no fields)
Used in:
Used in:
(message has no fields)
Used in:
See https://pkg.go.dev/github.com/docker/go-connections/nat#PortMap
Used in:
When zero in the CreateContainerRequest, docker will use a random port
Used in:
Used in:
Used in:
,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.
Used in:
Used in:
Used in:
Used in:
Used in:
,Used in:
Used in:
"" if no error
Used in:
Used in:
A identifier for that docker instance, see https://docs.docker.com/engine/api/v1.43/#tag/System/operation/SystemInfo