docker-helper

Executes Docker builds, pulls, and container runs through a policy-enforcing daemon without direct docker.sock access.

Updated Aug 8, 2026
One-click install
npx skills add https://github.com/kivarun/docker-helper --skill docker-helper-kivarun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker-helper
Source: https://github.com/kivarun/docker-helper/tree/main/.claude/skills/docker-helper
Command: npx skills add https://github.com/kivarun/docker-helper --skill docker-helper-kivarun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coding agents that need to build images and run containers cannot safely receive direct access to docker.sock, since that grants unrestricted host filesystem and network access. Docker Helper mediates all Docker operations through a policy-enforcing daemon that restricts build contexts and mount sources to the session's issued filesystem snapshot. ## Core Features & Use Cases - Mediated Docker Operations: Pull images, build from Dockerfiles, and run containers through the docker-helper CLI or the HTTP API over the Docker Helper Unix socket, authenticated by a session token. - Session and Credential Management: Create sessions scoped to a workspace plus issued filesystem roots using Launcher or Principal credentials, and introspect your own authority with docker-helper self or GET /self. - Policy-Aware Mounting: Enforces path containment on canonical mount sources, distinguishing invalid_mount rejections from read_only_root policy refusals. - Use Case: An agent in a sandboxed environment needs to build an image and run a test container. It uses the provisioned DOCKER_HELPER_SESSION_TOKEN to call docker-helper build and docker-helper run, mounting only the session workspace, without ever touching docker.sock. ## Quick Start Use the docker-helper skill to pull the alpine image and run a container that mounts the current workspace at /workspace.

Frequently Asked Questions about docker-helper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a Docker container without access to docker.sock?

Use the docker-helper CLI or its HTTP API over the Docker Helper Unix socket with a session token. Run docker-helper run --mount .:/workspace IMAGE -- command, and the daemon enforces mount policy on your behalf.

How do I build a Docker image through Docker Helper?

Run docker-helper build . --dockerfile Dockerfile --image IMAGE with your session token in DOCKER_HELPER_SESSION_TOKEN. The build context must resolve inside your session workspace, and the CLI streams operation output until completion.

Can I use Docker Helper without the CLI installed?

Yes, the HTTP API over the Docker Helper Unix socket is a first-class interface with the same capabilities. Send POST requests to /pull, /build, and /run with an Authorization Bearer header fed to curl via its header-from-stdin form.

Why does Docker Helper reject my mount with invalid_mount or read_only_root?

invalid_mount means the mount source violates structural or containment rules, such as an absolute path outside the issued session snapshot. read_only_root means the session policy forbids writable exposure; request the source read-only or report the policy limitation instead of retrying.

What are the limitations of a Docker Helper session token?

A session token only authorizes data-plane operations like pull, build, run, and registry login. It cannot create, list, show, or delete sessions, which require a Launcher or Principal credential, and it cannot access operator commands.