docs: fix remaining install issues — stale versions, Docker TOC, ARM note, frontmatter

This commit is contained in:
Vincent Koc
2026-03-19 11:42:57 -07:00
parent 30ddeabfdc
commit e5b50ba0d5
8 changed files with 26 additions and 3 deletions

View File

@@ -71,6 +71,10 @@ ENV NODE_ENV=production
CMD ["node","dist/index.js"]
```
<Note>
The download URLs above are for x86_64 (amd64). For ARM-based VMs (e.g. Hetzner ARM, GCP Tau T2A), replace the download URLs with the appropriate ARM64 variants from each tool's release page.
</Note>
## Build and launch
```bash

View File

@@ -23,6 +23,12 @@ This guide covers:
Sandboxing details: [Sandboxing](/gateway/sandboxing)
## On this page
- [Containerized Gateway](#containerized-gateway-docker-compose) — run the full OpenClaw Gateway in Docker
- [Agent Sandbox](#agent-sandbox-host-gateway--docker-tools) — isolate agent tool execution in containers while the gateway runs on the host
- [Troubleshooting](#troubleshooting)
## Requirements
- Docker Desktop (or Docker Engine) + Docker Compose v2

View File

@@ -180,7 +180,7 @@ Designed for environments where you want everything under a local prefix (defaul
<Steps>
<Step title="Install local Node runtime">
Downloads a pinned supported Node tarball (currently default `22.22.0`) to `<prefix>/tools/node-v<version>` and verifies SHA-256.
Downloads a pinned supported Node LTS tarball (the version is embedded in the script and updated independently) to `<prefix>/tools/node-v<version>` and verifies SHA-256.
</Step>
<Step title="Ensure Git">
If Git is missing, attempts install via apt/dnf/yum on Linux or Homebrew on macOS.

View File

@@ -138,7 +138,7 @@ OPENCLAW_NAMESPACE=my-namespace ./scripts/k8s/deploy.sh
Edit the `image` field in `scripts/k8s/manifests/deployment.yaml`:
```yaml
image: ghcr.io/openclaw/openclaw:2026.3.1
image: ghcr.io/openclaw/openclaw:latest # or pin to a specific version from https://github.com/openclaw/openclaw/releases
```
### Expose beyond port-forward

View File

@@ -1,4 +1,8 @@
---
summary: "Deploy OpenClaw on Northflank with one-click template"
read_when:
- Deploying OpenClaw to Northflank
- You want a one-click cloud deploy with browser-based setup
title: Deploy on Northflank
---

View File

@@ -1,4 +1,8 @@
---
summary: "Deploy OpenClaw on Railway with one-click template"
read_when:
- Deploying OpenClaw to Railway
- You want a one-click cloud deploy with browser-based setup
title: Deploy on Railway
---

View File

@@ -1,4 +1,8 @@
---
summary: "Deploy OpenClaw on Render with Infrastructure-as-Code"
read_when:
- Deploying OpenClaw to Render
- You want a declarative cloud deploy with Render Blueprints
title: Deploy on Render
---

View File

@@ -21,8 +21,9 @@ deployments work at a high level.
- **GCP (Compute Engine)**: [GCP](/install/gcp)
- **Azure (Linux VM)**: [Azure](/install/azure)
- **exe.dev** (VM + HTTPS proxy): [exe.dev](/install/exe-dev)
- **AWS (EC2/Lightsail/free tier)**: works well too. Video guide:
- **AWS (EC2/Lightsail/free tier)**: works well too. Community video guide:
[https://x.com/techfrenAJ/status/2014934471095812547](https://x.com/techfrenAJ/status/2014934471095812547)
(community resource, may become unavailable)
## How cloud setups work