DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Docker — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
D

dsh-docker

Docker

DeepSeek Harness 插件:通过本地 Docker CLI 为代理提供 Docker 容器、镜像、日志和 Compose 工具

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:DevViking-Persike/dsh-docker#0ca109e9c08828428a878b90708c44ba9dbc868a
README兼容性版本

兼容性与来源证明

Docker 以 dsh-docker 发布,当前版本为 0.1.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
github
Registry 更新时间
2026/8/22

版本

0.1.0stable
2026/8/22

相关插件

正在加载相关插件…

最新版
0.1.0
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
any
许可证
MIT
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/8/22
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 developer-tools 分类下经过校验的插件。

Web App@deepseek-ai/dsh-web-appdsh 浏览器界面捆绑包:位于 dsh-base 之上的 Web 补丁层,加上运行时粘合插件(提供前端 dist、Web 界面提示符、bash 运行时变量和 URL 行)Sdk Minimal@deepseek-ai/dsh-sdk-minimal独立的最小 SDK 配置包:JSON-RPC、一个 DeepSeek 适配器、持久化 Shell 和 JSONL 会话Sdk App@deepseek-ai/dsh-sdk-appdsh SDK 配置包:基于 dsh-base 提供 stdio JSON-RPC 服务和进程生命周期管理Subagent Codex@deepseek-ai/dsh-subagent-codex基于官方 app-server 协议的一次性 Codex 子代理提供程序

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.