SkillAgentSearch skills...

deepseek-harness-docker

Deploy, configure, verify, upgrade, and troubleshoot DeepSeek Harness with the community Docker, Docker Compose, rootless Podman, and Helm runtime, including the built-in Chromium/noVNC browser, optional protected LAN gateway, optional ungoogled-chromium image, and optional plugin market

Install / Use

npx skills add runzhliu/deepseek-harness-docker

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

79/100

Category

Operations

Supported Platforms

Universal

Our assessment of deepseek-harness-docker

deepseek-harness-docker scores 79/100 on our quality scale, 675th of 745 Operations skills we index.

Its SKILL.md is 7.0 KB long, well organised into 11 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
0/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so deepseek-harness-docker is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-15. Automated pattern scan on 2026-11-15. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

deepseek-harness-docker compared with similar skills

All 4 of these similar skills score higher than deepseek-harness-docker; compare them before choosing.

SkillScoreStarsUpdatedFormat
deepseek-harness-docker (this skill)by runzhliu7903d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
LocalAIby mudler10050.4ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install deepseek-harness-docker?
Run npx skills add runzhliu/deepseek-harness-docker. The install tabs above show the steps for each supported agent.
Which AI agents does deepseek-harness-docker work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is deepseek-harness-docker safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is deepseek-harness-docker still maintained?
The repository was last updated 3 days ago, so deepseek-harness-docker is actively maintained.

name: deepseek-harness-docker description: Deploy, configure, verify, upgrade, and troubleshoot DeepSeek Harness with the community Docker, Docker Compose, and Helm runtime, including the built-in Chromium/noVNC browser and optional plugin market. Use when users ask to run DSH or DeepSeek Harness locally or on Kubernetes, mount a writable workspace, configure model credentials safely, enable the embedded browser, choose the market image, or diagnose container health and startup problems.

DeepSeek Harness Docker

Use the public runzhliu/deepseek-harness-docker project as the source of truth. Treat it as a community containerization project around the official @deepseek-ai/dsh npm package, not as an official DeepSeek image.

Preserve the security boundary

  • Bind WebUI port 3080 and noVNC port 6080 to 127.0.0.1 only.
  • Never create a public Ingress, LoadBalancer, NodePort, unrestricted -p 3080:3080, privileged container, or Docker socket mount.
  • Pass provider keys only at runtime through the Harness settings page, environment variables, .env, or Kubernetes Secrets. Never write credentials into Dockerfiles, images, Compose files committed to Git, logs, or answers.
  • Keep the named dsh-home volume unless the user explicitly asks to delete all Harness settings, credentials, sessions, and browser state.
  • Mount only the workspace the user authorizes. Do not broaden a bind mount to a home directory or filesystem root.
  • Treat the optional plugin market and every installed plugin as third-party code with access to the mounted workspace and persisted Harness profile.

Locate the deployment files

Use the current checkout when it contains compose.yaml and Dockerfile. Otherwise clone the public repository:

git clone https://github.com/runzhliu/deepseek-harness-docker.git
cd deepseek-harness-docker

Read README.md, SECURITY.md, compose.yaml, and .env.example before changing defaults. Prefer the repository's pinned image and DSH versions; do not silently switch to latest.

Choose the smallest suitable mode

Use default Compose for a local, single-user WebUI with the embedded Chromium desktop. Add compose.market.yaml only when the user explicitly wants the community plugin market. Use headless mode for one-shot automation and Helm only when the user requests Kubernetes.

Start the default local runtime

  1. Confirm Docker and Compose are available:

    docker version
    docker compose version
    
  2. Resolve the requested workspace to an absolute path and confirm it is the intended writable directory.

  3. Pull and start without rebuilding unless the user asks for a local source build:

    DSH_WORKSPACE=/absolute/path/to/project docker compose pull
    DSH_WORKSPACE=/absolute/path/to/project docker compose up -d --no-build
    docker compose ps
    
  4. Wait for the deepseek-harness service to become healthy. Verify both surfaces:

    curl --fail http://127.0.0.1:3080/
    curl --fail http://127.0.0.1:6080/vnc.html
    docker compose logs --tail=120 deepseek-harness
    
  5. Tell the user to open http://127.0.0.1:3080. Configure the model provider and key in Harness settings. Use the WebUI browser action for the embedded Chromium desktop; use http://127.0.0.1:6080/vnc.html?autoconnect=1 only as a direct fallback.

Enable the optional plugin market

Keep the default image unchanged and opt in through the overlay:

DSH_WORKSPACE=/absolute/path/to/project \
  docker compose -f compose.yaml -f compose.market.yaml pull
DSH_WORKSPACE=/absolute/path/to/project \
  docker compose -f compose.yaml -f compose.market.yaml up -d --no-build
docker compose -f compose.yaml -f compose.market.yaml ps

If the market reports a pnpm store version mismatch, stop the service and run the repository's explicit repair command from README.md. Do not delete the profile or named volume as a shortcut.

Run a headless task

Use the pinned image and pass the provider key from the existing environment without printing it:

docker run --rm \
  --env DEEPSEEK_API_KEY \
  --mount type=volume,src=dsh-home,dst=/home/node/.dsh \
  --mount type=bind,src=/absolute/path/to/project,dst=/workspace \
  runzhliu/deepseek-harness:0.1.2-alpha.4-r1 \
  --profile headless "summarize this repository"

Replace the provider environment variable and model configuration only when the selected provider requires it. Keep secrets out of command output and shell history where possible.

Deploy with Helm

Use the included chart as a single-replica, stateful, private deployment:

helm lint --strict charts/deepseek-harness
helm upgrade --install deepseek-harness charts/deepseek-harness \
  --namespace deepseek-harness \
  --create-namespace
kubectl -n deepseek-harness rollout status statefulset/deepseek-harness
kubectl -n deepseek-harness port-forward service/deepseek-harness 3080:3080 6080:6080

Use an existing Secret for provider credentials and an existing PVC when a persistent writable workspace is required. Preserve the chart's private Service and NetworkPolicy defaults.

Build or upgrade safely

  • Run make verify before building changes.
  • Run make build and make smoke for the default image.
  • Run make market-build and make market-smoke for the optional market image.
  • On version upgrades, update every pinned DSH/image reference together, inspect upstream release notes, and rerun the full verification. Do not publish an unverified tag or a drifting latest tag.
  • Confirm both linux/amd64 and linux/arm64 when publishing multi-platform images.

Diagnose failures

Start with non-destructive evidence:

docker compose config
docker compose ps
docker compose logs --tail=200 deepseek-harness
docker compose ps -q deepseek-harness

Pass the container ID reported by the last command to docker inspect; do not assume a fixed Compose project name.

Check these common boundaries:

  • 3080 or 6080 already in use: choose different loopback host ports through DSH_PORT or DSH_DESKTOP_PORT.
  • Workspace not writable: verify the exact bind source and its ownership instead of making broad host directories writable.
  • Browser unhealthy: verify /dev/shm, the 6080 endpoint, and the 9222 Chromium debug endpoint from inside the container.
  • Profile or plugin failure: inspect the persisted profile and plugin logs before repairing; preserve backups created by the market repair tool.
  • Model request failure: verify provider URL, model name, and the presence of the expected environment variable without revealing its value.

Do not use docker compose down --volumes, remove named volumes, or overwrite profile files without explicit user approval and a clear explanation of the data loss.

Report completion

State the selected image tag, workspace mount, exposed loopback URLs, container health, and verification performed. Distinguish a successful WebUI health check from a successful real model/tool call; perform the latter only when the user supplied a provider configuration and authorized the test.

Related Skills

View on GitHub
GitHub Stars0
CategoryOperations
Updated3d ago
Forks0

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low