Shared building blocks for the tagwright suite. The first piece is runtime, a
container-runtime abstraction over Docker and Podman. It talks to a Docker Engine
API-compatible socket and exposes the operations the suite's tools need: list and
inspect containers, watch the socket for lifecycle events, read compose
project/service labels, stop and start containers, exec into them, and a set of
normalized Container and Mount types so callers do not deal in engine-specific
shapes. A single request-and-mapping core is shared by a Docker adapter and a
Podman adapter that differ only in their default socket path and how they read
compose identity off a container's labels.
This module is a leaf: its only non-stdlib dependency is the Docker SDK. It was
extracted from ballast so a second consumer can share the same abstraction.
Package runtime abstracts a container runtime (Docker or Podman) behind the small set of operations Ballast needs: discover containers and their mounts, watch the socket for lifecycle changes, exec into a container to quiesce or dump it, and stop or start it for a cold backup.
Package runtime abstracts a container runtime (Docker or Podman) behind the small set of operations Ballast needs: discover containers and their mounts, watch the socket for lifecycle changes, exec into a container to quiesce or dump it, and stop or start it for a cold backup.
Click to show internal directories.
Click to hide internal directories.
go.dev uses cookies from Google to deliver and enhance the quality of its services and to
analyze traffic. Learn more.