mirror of
https://github.com/openclaw/openclaw.git
synced 2026-04-18 06:37:29 +00:00
docs(docker): note legacy gateway.bind alias migration
This commit is contained in:
@@ -33,6 +33,12 @@ Sandboxing details: [Sandboxing](/gateway/sandboxing)
|
||||
|
||||
### Quick start (recommended)
|
||||
|
||||
<Note>
|
||||
Docker defaults here assume bind modes (`lan`/`loopback`), not host aliases. If your
|
||||
existing config still uses `gateway.bind` host aliases like `0.0.0.0` or `localhost`,
|
||||
OpenClaw now auto-migrates them to supported bind modes on startup/doctor.
|
||||
</Note>
|
||||
|
||||
From repo root:
|
||||
|
||||
```bash
|
||||
@@ -416,6 +422,10 @@ pnpm test:docker:qr
|
||||
The setup script also pins `gateway.mode=local` after onboarding so Docker CLI
|
||||
commands default to local loopback targeting.
|
||||
|
||||
Legacy config note: host aliases in `gateway.bind` (`0.0.0.0`, `127.0.0.1`,
|
||||
`localhost`, `::`, `::1`) are migrated to bind modes (`lan` / `loopback`) during
|
||||
startup and `openclaw doctor`.
|
||||
|
||||
If you see `Gateway target: ws://172.x.x.x:18789` or repeated `pairing required`
|
||||
errors from Docker CLI commands, run:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user