feat(docker): support offline setup reruns (#89062) · ope...
Alix-007
·
2026-06-17
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -46,6 +46,29 @@ Docker is **optional**. Use it only if you want a containerized gateway or to va
|
46 | 46 | |
47 | 47 | </Step> |
48 | 48 | |
| 49 | + <Step title="Airgapped rerun"> |
| 50 | +On offline hosts, transfer and load the image first: |
| 51 | + |
| 52 | +```bash |
| 53 | +docker load -i openclaw-image.tar |
| 54 | +export OPENCLAW_IMAGE="ghcr.io/openclaw/openclaw:latest" |
| 55 | +./scripts/docker/setup.sh --offline |
| 56 | +``` |
| 57 | + |
| 58 | +`--offline` verifies that `OPENCLAW_IMAGE` already exists locally, disables |
| 59 | +implicit Compose pulls and builds, then runs the normal setup flow such as |
| 60 | +`.env` synchronization, permission fixes, onboarding, gateway config sync, |
| 61 | +and Compose startup. |
| 62 | + |
| 63 | +If `OPENCLAW_SANDBOX=1`, offline setup also checks the configured default |
| 64 | +and active per-agent sandbox images on the daemon behind |
| 65 | +`OPENCLAW_DOCKER_SOCKET`. Docker-backed browser images must also carry the |
| 66 | +current OpenClaw browser contract label. When a required image is missing or |
| 67 | +incompatible, setup exits without changing sandbox configuration instead of |
| 68 | +reporting success with an unusable sandbox. |
| 69 | + |
| 70 | + </Step> |
| 71 | + |
49 | 72 | <Step title="Complete onboarding"> |
50 | 73 | The setup script runs onboarding automatically. It will: |
51 | 74 | |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
