DeepSeek Harness Docker Services

Open-source-ready guarded Docker operations for DeepSeek Harness (DSH). The
repository separates the DSH client plugin from a privileged controller. It is
for teams that want useful inventory, health, resources, logs, lifecycle,
parameter, secret, and deploy controls without exposing raw Docker, shell, or
remote-host access to the UI or model.

What it provides

• Inventory displays controlled and unmanaged containers, status/health,
  resource fields, image/digest, deployment repo/branch/SHA/time/test state,
  and an optional internal or Tailscale URL.
• Per-service action allowlists cover logs, start/stop/restart, schema-driven
  non-secret parameters, and write-only secret status/set/rotate/test.
• Deploy calls are exact-revision guarded (repo, branch, full SHA), leased and
  idempotent. Only authoritative hook output can supply image digest, verified
  reachability/branch binding, deployment time, and passing test state.
• Local Docker, constrained SSH helper, and mTLS JSON adapter reference
  implementations; all use typed operations only.
• Signed trusted-proxy identity/RBAC, bounded opaque errors, protected redacted
  logs, fsynced hash-chained audit with keyed checkpoints, atomic no-follow
  writes, package/consumer/container checks, and CI.
• A fixed-identity local proxy gives Harness only a private, authenticated
  socket; the signing key and controller socket remain outside Harness.

Quick start

npm ci --ignore-scripts
npm run ci
cp examples/controller.json /etc/dsh-docker-services/controller.json
cp examples/proxy.json /etc/dsh-docker-services/proxy.json

Then replace the example values, create the dedicated controller account and
hooks, and follow deployment instructions. Read the
threat model before granting Docker/socket access.

Project layout

• packages/plugin: DSH plugin; no Docker or secret filesystem access.
• packages/controller: privileged allowlist enforcement and adapters.
• packages/proxy: unprivileged fixed-identity HMAC bridge for one Harness domain.
• packages/shared: versioned protocol and configuration validation.
• examples: host unit, container deployment, and generic configuration.

This project intentionally does not ship a universal deploy script: deployment
semantics are workload-specific and must be reviewed as administrator-owned,
fixed hooks. See releasing for artifact separation.