Overview

OpenClaw is an agent gateway for running AI-assisted workflows, tools, and integrations in a persistent environment. DockerCP deploys the published gateway image, stores its configuration and workspace in a named volume, generates a gateway token, maps the gateway port, and prepares Linux host access for supported local integrations.

Docker image ghcr.io/openclaw/openclaw:latest
Default port 18789
Deployment type docker image
Recommended resources 2 CPU · 4 GB

How deployment works in DockerCP

This template gives DockerCP the deployment metadata needed to create a service, prepare runtime variables, map persistent storage, expose the internal port, and connect a public domain with SSL when required.

  1. Create or select a project where the service belongs
  2. Review the Docker image, tag, default port, environment variables, and volume mappings
  3. Deploy the service and check logs until the application is healthy
  4. Attach a domain or subdomain when the application must be available publicly
  5. Enable HTTPS and verify the final browser response

Configuration

Environment variables

Variable Default / guidance
HOME /home/node
OPENCLAW_HOME /home/node
OPENCLAW_STATE_DIR /home/node/.openclaw
OPENCLAW_CONFIG_PATH /home/node/.openclaw/openclaw.json
OPENCLAW_CONFIG_DIR /home/node/.openclaw
OPENCLAW_WORKSPACE_DIR /home/node/.openclaw/workspace
OPENCLAW_GATEWAY_PORT 18789
OPENCLAW_GATEWAY_TOKEN change_me
TZ UTC

Persistent volumes

Volume Mount path
openclaw_data /home/node/.openclaw

Commands

DockerCP handles deployment from the panel, but understanding the equivalent Docker commands helps users debug services with more confidence. 

docker pull ghcr.io/openclaw/openclaw:latest
docker ps --filter "name=openclaw"

docker logs --tail=100 openclaw

DNS and SSL checklist

Step Expected result
Add A or CNAME record The domain points to the DockerCP server or configured target
Attach domain to service The service is reachable through the selected hostname
Enable HTTPS The certificate becomes active and redirect to HTTPS can be enabled

Screenshots

Panel previews for the OpenClaw template: how deployment, the running service, and its key details look inside DockerCP.

OpenClaw deployment form inside the DockerCP panel
Automation workflows running on the deployed service
Public webhook URL routed through the DockerCP proxy

Troubleshoot

  • Confirm the Docker image and tag exist
  • Confirm the selected internal port matches the application port
  • Confirm required variables such as database URL, app URL, and credentials are set
  • Check service logs after the first deployment
  • Verify DNS before requesting or renewing SSL certificates