Package-level declarations
Types
Discovery, logs and controls for existing Compose containers. No CLI or source files are needed. The caller owns the supplied client; this integration never closes it. HTTP failures return SDK errors; transport/decoding failures and cancellation propagate. Snapshots are not atomic: a container removed between list and inspect can fail discovery.
Metadata from labels and inspect. Nullable metadata remains unknown, never guessed from names. state retains Docker health separately from running status; running does not imply healthy. Labels and daemon data are untrusted and may contain sensitive information.
SDK response paired with the pre-operation snapshot. Errors retain context; start/stop HTTP 304 becomes success.
Container-backed discovery snapshot. No desired configuration or readiness is inferred.
Engine operations on existing containers; these are not Compose up/down.
Completed batch; inspect results even when the enclosing SDK Result is successful.
Observed services plus containers whose service label is absent or blank.
Observed containers, including stopped replicas, one-offs and unknown one-off metadata.