DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

Docker — DSH Plugin for DeepSeek Harness
DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in
← Plugins
D

dsh-docker

Docker

DeepSeek Harness plugin: Docker container, image, log, and Compose tools for the agent, over the local Docker CLI

The plugin will be installed here. Keep web if you are unsure.

npx -y @deepseek-ai/dsh plugin --profile web add github:DevViking-Persike/dsh-docker#0ca109e9c08828428a878b90708c44ba9dbc868a
READMECompatibilityVersions

Compatibility and provenance

Docker is published as dsh-docker and currently resolves to version 0.1.0. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.

DSH compatibility
*
Runtime surfaces
any
Release source
github
Registry updated
8/22/2026

Versions

0.1.0stable
8/22/2026

Related plugins

Loading related plugins…

Latest
0.1.0
DSH
*
HMR
Process restart
Tree shaking
Safe tree shaking not declared
Unpacked size
Unavailable
Files
Unavailable
Surface
any
License
MIT
Source
github
GitHub
★ 0
Weekly downloads
0
Last push
8/22/2026
View source ↗
README badge

Click the badge to copy Markdown for your README.

Do you maintain this Plugin?Claim benefit · Priority security scan

Verify the GitHub repository declared in package.json to manage this listing. After you claim it, Hub will prioritize a security scan of the current version and publish the result when it passes.

Claim this Plugin →
Report an issue

Related plugins

More verified plugins in developer-tools.

Web App@deepseek-ai/dsh-web-appThe dsh browser-surface bundle: the web patch layer over dsh-base plus the runtime glue plugin (frontend dist serving, web-surface prompt, bash runtime variables, URL line)Sdk Minimal@deepseek-ai/dsh-sdk-minimalThe standalone minimal SDK profile bundle: JSON-RPC, one DeepSeek adapter, persistent shell, and JSONL sessionsSdk App@deepseek-ai/dsh-sdk-appThe dsh SDK profile bundle: stdio JSON-RPC serving and process lifecycle over dsh-baseSubagent Codex@deepseek-ai/dsh-subagent-codexOne-shot Codex subagent provider over the official app-server protocol

README

dsh-docker

Docker tools for DeepSeek Harness: the agent can list containers, read logs, inspect images, and drive Compose projects, all through the Docker CLI already on the machine.

No daemon is required at install time. Reachability is probed per call, so a machine without Docker simply reports an unreachable engine instead of failing to load.

Install

dsh plugin --profile web add github:DevViking-Persike/dsh-docker

Restart dsh afterwards. The read-only tools are active immediately; see Compose to enable the lifecycle tools.

Tools

ToolWhat it does
docker_psList containers. Running only by default; all: true includes stopped ones, project filters to one Compose project.
docker_imagesList local images with their tags and sizes.
docker_logsRead a container's recent output. Keeps the newest text and reports when older entries were dropped.
docker_compose_upStart a Compose project detached and wait for its containers. Opt-in.
docker_compose_downStop and remove a Compose project's containers. Opt-in.

Compose lifecycle

Starting and stopping containers changes machine state, so those two tools are off by default. A deployment that wants them sets compose: true:

- id: dsh-docker
  name: 'dsh-docker'
  config:
    compose: true

Configuration

Every field is optional.

FieldDefaultMeaning
clidockerExecutable name or absolute path.
projectRootprocess cwdWorking directory for invocations, and the root relative compose paths resolve against.
composefalseRegister the Compose lifecycle tools.
inspectTimeoutMs30000Budget for one read (ps, images, logs).
composeTimeoutMs600000Budget for one Compose call; pulling images and waiting on health checks routinely outlasts a read by an order of magnitude.
maxOutputBytes2000000Cap on collected output of one invocation.
maxLogChars40000Cap on characters docker_logs emits.
defaultLogTail200Trailing lines read when a request states no tail.
graceMs5000Termination grace handed to the subprocess seam.

Model Experience

The read-only tools put one line per container or image into the model's context, not raw CLI output: state, status, image, Compose project/service, and published ports. An empty result says so explicitly rather than returning blank text, so the model does not read silence as failure.

docker_logs keeps the newest characters when it must cut, because the tail of a log is what explains a failure that just happened, and it marks the cut so the model knows it is not seeing the whole file.

Compose results lead with the settled project state and put the backend's own output after it — the model reasons about which containers are up, and reads the CLI text only when diagnosing.

Safety

  • Arguments reach the executable as a fixed argv and are never shell-interpreted, so a container name cannot become a flag or a shell fragment.
  • -- terminates flag parsing before every container operand, so a container literally named --follow stays an operand.
  • docker_compose_down never forwards a service filter: down removes the whole project, and a filtered call would read as narrower than it is.
  • Compose lifecycle calls are marked concurrency-unsafe, because two lifecycle calls on one project race inside the engine.

Known Limitations and Deferred Work

  • Image sizes are parsed from the CLI's display string (1.09GB), because docker images --format json exposes no machine-readable size. An unparseable value reads as 0 rather than failing the listing.
  • Engine reachability is probed on every call rather than cached, so a stopped daemon is noticed immediately at the cost of one extra invocation per tool call.
  • Compose project state is read back with a second docker ps after each lifecycle call, since the CLI's own output does not report the settled containers.
  • There is no docker exec, no image build, and no registry operation. Each would widen the blast radius considerably and none has a current consumer.

License

MIT — see LICENSE and NOTICE.md for attribution to the DeepSeek Harness project whose plugin conventions this follows.