48 lines
1.9 KiB
Markdown
48 lines
1.9 KiB
Markdown
# Runbook: Incidentes OpenClaw Browser/CDP
|
|
|
|
Historial resumido de incidentes previos con OpenClaw y su browser container.
|
|
|
|
## Sintomas comunes
|
|
|
|
- Browser container aparece `unhealthy`.
|
|
- OpenClaw no conecta al browser via CDP.
|
|
- Timeouts contra el puerto CDP.
|
|
|
|
## Diagnostico
|
|
|
|
```powershell
|
|
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "pct exec 102 -- docker ps --format 'table {{.Names}}\t{{.Status}}\t{{.Ports}}' | grep -E 'openclaw|browser'"
|
|
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "pct exec 102 -- docker exec <browser-container> ss -tlnp"
|
|
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "pct exec 102 -- docker logs <browser-container> --tail 100"
|
|
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "pct exec 102 -- docker logs <openclaw-container> --tail 100"
|
|
```
|
|
|
|
## Puerto CDP
|
|
|
|
En un incidente previo, Chromium escuchaba en `127.0.0.1:9222` dentro del
|
|
container y nginx exponia `0.0.0.0:9223` para otros containers. No asumas que
|
|
`9222` o `9223` es correcto sin probar desde la red Docker actual.
|
|
|
|
Prueba desde el container OpenClaw:
|
|
|
|
```powershell
|
|
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "pct exec 102 -- docker exec <openclaw-container> curl -sf http://<browser-host>:9223/json/version"
|
|
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "pct exec 102 -- docker exec <openclaw-container> curl -sf http://<browser-host>:9222/json/version"
|
|
```
|
|
|
|
## Acciones que requieren confirmacion
|
|
|
|
```powershell
|
|
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "pct exec 102 -- docker exec <browser-container> pkill -f chromium"
|
|
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "pct exec 102 -- docker restart <browser-container>"
|
|
.\scripts\Invoke-ProxmoxSsh.ps1 -Command "pct exec 102 -- docker restart <openclaw-container>"
|
|
```
|
|
|
|
## Notas de configuracion
|
|
|
|
- Montar `/dev/shm` o usar `shm_size` suficiente suele mejorar estabilidad de
|
|
Chromium en Docker.
|
|
- Limpiar locks de perfil en startup puede resolver arranques atascados.
|
|
- Cambios de capacidades como `SYS_ADMIN` o `seccomp:unconfined` son sensibles;
|
|
revisarlos antes de aplicarlos.
|