mirror of
https://github.com/openclaw/openclaw.git
synced 2026-08-13 14:12:57 -06:00
2c3e537cb8
Three defects proven by running the shipped configs: Kubernetes probes checked only the status code against /startupz, but the pinned image predates that route and the Control UI answers unknown paths with a catch-all 200. A wedged pod was therefore marked Ready forever. Probes now assert the JSON probe contract and target routes the pinned image actually serves; verified in a kind cluster where the old command exits 0 on the missing route and the new one exits 1. render.yaml set no dockerCommand, so the image CMD ran without --allow-unconfigured and a fresh Render disk exited 78 with 'Missing config' before binding. Reproduced locally with Render's exact env. The Cloudflare Container readiness poll had the same route mismatch against operator-supplied official image digests; it now polls /healthz, which every published image serves. Also replaces an R2 verification step that could never fail: wrangler cannot list object keys, so the documented command 404'd into || true.
24 lines
725 B
YAML
24 lines
725 B
YAML
services:
|
|
- type: web
|
|
name: openclaw
|
|
runtime: docker
|
|
plan: starter
|
|
# The image CMD has no --allow-unconfigured, so a fresh disk with no
|
|
# openclaw.json exits before binding. Render has no shell before the first
|
|
# boot, so the flag has to come from the blueprint.
|
|
dockerCommand: node openclaw.mjs gateway --allow-unconfigured
|
|
healthCheckPath: /startupz
|
|
envVars:
|
|
- key: OPENCLAW_GATEWAY_PORT
|
|
value: "8080"
|
|
- key: OPENCLAW_STATE_DIR
|
|
value: /data/.openclaw
|
|
- key: OPENCLAW_WORKSPACE_DIR
|
|
value: /data/workspace
|
|
- key: OPENCLAW_GATEWAY_TOKEN
|
|
generateValue: true
|
|
disk:
|
|
name: openclaw-data
|
|
mountPath: /data
|
|
sizeGB: 1
|