Docker Compose + Gemini onboarding triage: start from docker-setup.sh baseline

Scenario: first-time Docker install fails before model/channel wiring. Reduce variables: run official docker setup flow first, validate dashboard pairing, then add Gemini and Telegram incrementally.

REDDITDiscovered 2026-02-14Author u/AliYa18

Prerequisites

Docker Engine/Desktop and Compose v2 are installed and healthy.
You can run commands from OpenClaw repo root (not a random subfolder).

Steps

Run ./docker-setup.sh to generate .env token, compose files, and baseline gateway service before custom edits.
Bring gateway up and fetch dashboard URL/token; approve pending device pairing if 1008 pairing required appears.
Only after baseline passes, configure model provider (Gemini) and Telegram channel one by one, testing each change immediately.
If browser-dependent tasks fail in Docker, install Playwright Chromium via bundled CLI path (not npx playwright).

Commands

./docker-setup.sh

docker compose run --rm openclaw-cli dashboard --no-open

docker compose run --rm openclaw-cli devices list

docker compose run --rm openclaw-cli devices approve <requestId>

docker compose run --rm openclaw-cli node /app/node_modules/playwright-core/cli.js install chromium

Verify

Gateway is reachable, dashboard authenticated, pairing approved, and test prompt works before adding advanced workflow changes.

Caveats

Do not copy unknown compose snippets from random posts before baseline works.
Gemini model availability and quotas depend on account/region; verify separately（需验证）.

Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗

Visit original post