deployment intermediate active

OpenClaw Docker CN IM

npm install hangs at 2KB/s behind the GFW. Every CN developer has wasted hours on this. Here's the fix.

openclaw docker china deployment cn im container

What breaks without openclaw docker china

npm timeouts on CN networks. DockerHub unreachable without mirrors. IM adapter setup duplicated per platform.

→
Zero-timeout OpenClaw install × CN-optimized Docker Compose with all IM adapters ÷ 30-minute setup ÷ no GFW workarounds needed = running bots inside China.

openclaw docker china — what it actually does

01
Packages OpenClaw with QQ, WeChat, DingTalk, and Feishu adapters pre-bundled.
02
Uses npmmirror.com and CN Docker registry mirrors to avoid GFW timeouts.
03
Runs as Docker Compose — one command starts the full CN-ready stack.
04
Pre-configures adapter credentials via .env without touching npm scripts directly.
05
Works on any Linux VPS with Docker, including CN datacenter instances.

Security check — openclaw docker china

Privacy score: 7/10 — accesses connected platform APIs only. Lock it: review OAuth scopes before install, confirm Docker ≥20.x, Docker Compose ≥2.x; OpenClaw ≥1.2; optimized for mainland China compatibility.

Quick start — openclaw docker china in 30–60 minutes

Setup time: 30–60 minutes

!
You need:
  • Docker
  • server or VPS with China mainland access
  • basic Docker Compose knowledge

Install the package:

git clone https://github.com/justlovemaki/openclaw-docker-cn-im
cd openclaw-docker-cn-im
docker compose up -d
1
Clone the repo
2
Configure .env with your IM platform credentials (QQ, WeChat, DingTalk, or Feishu)
3
Review docker-compose.yml and set image mirror if needed (e.g. registry.cn-hangzhou.aliyuncs.com)
4
Run docker compose up -d
5
Check logs with docker compose logs -f
6
Send a test message on your configured IM platform

Troubleshooting openclaw docker china

1
1. Using DockerHub images directly from China — often rate-limited or unreachable; use Aliyun or other CN mirrors
2
2. Not setting the correct timezone (TZ=Asia/Shanghai) — affects cron-based plugins
3
3. Missing npm registry config — set NPM_REGISTRY=https://registry.npmmirror.com inside the container

Compatibility & status

Works with: Docker ≥20.x, Docker Compose ≥2.x; OpenClaw ≥1.2; optimized for mainland China intermediate Last updated: Oct 2025 ★ 260 on GitHub MIT

Official docs →

View on GitHub →

FAQ — openclaw docker china

Does this work outside of China?

Yes, but there's no benefit — the CN mirror configurations add unnecessary indirection on global networks.

Can I add additional plugins to the Docker image?

Yes. Add them to the package.json in the repo and rebuild the image, or mount a local plugins directory.

Does this include the Lobster dashboard?

Yes, Lobster is included and mapped to a configurable port in the Compose file.

Related — more like openclaw docker china

Openclaw Qqbot
From OpenClaw logic to QQ groups and DMs — the official Tencent-maintained QQ adapter.
OpenClaw WeChat
From OpenClaw logic to WeChat — an adapter for building bots on China's dominant messaging platform.
Openclaw Channel Dingtalk
From OpenClaw events to DingTalk workspaces — enterprise-grade messaging integration for Alibaba's platform.
Openclaw Feishu
From OpenClaw workflows to Feishu/Lark — ByteDance's enterprise platform, fully integrated.
OpenClaw Setup CN
Step-by-step OpenClaw setup guide optimized for mainland China network conditions.

Every hour spent fighting CN registry timeouts is an hour not building your bot.

Teams without this setup spend their first day on installation, not code.

Get it on GitHub →