kivarum

It covers pulling images, building images, running containers, and registry authentication when direct Docker or docker.sock access is unavailable. It also addresses delegated Session creation, issued filesystem scope across workspace and roots, and authority checks through self or GET /self.

Platform engineers, DevOps practitioners, and cloud operators working in restricted compute environments benefit most. It fits cases where Docker actions must occur through delegated credentials rather than local daemon access, especially when registry sign-in, image builds, container runs, and scope verification are required.

Start only where the delegated Docker service is present. If the environment provisions a Launcher or Principal credential, create a Session, use its issued workspace and filesystem roots, then perform image, registry, and container actions. Use self or GET /self to confirm granted authority.

The provided manifest does not state a license, repository terms, price, or usage fee. Treat licensing and cost as unspecified until the publisher adds explicit terms. Evaluate redistribution, commercial use, and support expectations only after those details are published.

You need an environment where the delegated Docker service is available and direct Docker or docker.sock access is not assumed. For delegated Session creation, the environment must provision a Launcher or Principal credential; issued scope is limited to workspace plus filesystem roots.