Real Skill packageSource verifiedClawHub registry

OpenClaw Docker Linux

Run OpenClaw inside Docker on Linux with Tailscale remote access. ⚠️ Involves sudo, Docker, Tailscale, and credential mounting — review security section before use. Complete setup guide covering installation, configuration, and critical gotchas. Trigger phrases: docker openclaw, openclaw in docker, setup openclaw docker, tailscale openclaw, docker-compose openclaw.

Identity and source

Publisher attributionDeonte Cooperregistry owner unverified by skillvetai
Functional categoryAgent Engineering, Security & Governanceautomatically inferred · 58% rule confidence
Package forminstruction with code9 recorded files
Canonical sourceClawHub registryclawhub:djc00p:openclaw-docker-linux
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 11/5/2026.claude/skills/openclaw-docker-linux

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 11/5/2026.agents/skills/openclaw-docker-linux

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 11/5/2026skills/openclaw-docker-linux

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.

clawhub install @djc00p/openclaw-docker-linux
clawhub inspect @djc00p/openclaw-docker-linux --version 1.0.16

Security evidence

SkillVetAI static result: no findings detected

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
9 / 9 inspected as text
Checked
11/5/2026, 6:40:25 AM
Scanner
0.1.3
Policy
1.0.3
3 inferred permission indicators
  • network access — automatically inferred
  • filesystem write — automatically inferred
  • credential access — automatically inferred
6 dependency and API indicators
  • api: 100.x.x.x
  • api: 192.168.1.x
  • api: clawhub.ai
  • api: clawhub.com
  • api: docs.docker.com
  • api: pkgs.tailscale.com
External clawhub result: clean

This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.

Evidence checked
11/5/2026, 12:40:11 AM
Release binding
Matches this record
  • skillspector: suspicious
  • llm: clean

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:2570d357fdae0d94d8eba6c21320ef43899f7d5e478f560945e960cc0c7dc2f3
Show up to 9 recorded paths
  • references/common-usage.md
  • references/docker-config.md
  • references/docker-setup.sh
  • references/gotchas.md
  • references/quickstart.md
  • references/start.sh
  • references/troubleshooting.md
  • skill-card.md
  • SKILL.md

Source changelog

Fix Tailscale Serve teardown: use the documented trailing-off syntax so the remote route is actually removed, stop suppressing the failure, and report explicitly when a stale Serve route remains. Serve setup now verifies the route started before claiming success.

Release security diff

mediumCompared fixed releases 1.0.10 and 1.0.16; 0 finding and 0 permission indicators were added.

Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.

Change reasons and limitations
  • dependency surface changed
  • file surface changed
  • content hash changed

Observed release history

These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.

1.0.1011/4/2026sha256:e7e69d54dab044d7b938958f7b9fd3ea2301980579f0b035602e5f7f9d75627c