openclaw - 💡(How to fix) Fix [Bug]: [2026.4.5] CLI SIGTERM after ~10s via exec/runtime wrapper (OPENCLAW_SHELL=exec path) [2 comments, 2 participants]

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading from 2026.4.2 to 2026.4.5, all CLI subcommands beyond --version are killed with SIGTERM after ~10 seconds when executed inside the Docker container.

Steps to reproduce

1. Run OpenClaw 2026.4.5 in Docker with gateway bound to lan (0.0.0.0:18789)
2. Exec into the running container: docker compose exec <service> node dist/index.js gateway status --json --no-probe
3. Observe process exits with SIGTERM after ~10 seconds with no output

Expected behavior

On 2026.4.2, openclaw gateway status returned gateway status JSON immediately. CLI subcommands functioned normally inside the container.

Actual behavior

Every CLI subcommand beyond --version exits with SIGTERM after ~10 seconds. No output or error message is produced. Gateway itself remains fully functional (Telegram, cron, web dashboard all working).

OpenClaw version

2026.4.5

Operating system

Debian GNU/Linux 12 (Docker container, host is VPS)

Install method

Docker / Docker Compose

Model

anthropic/claude-sonnet-4-6

Provider / routing chain

openclaw -> anthropic

Additional provider/model setup details

Primary model is anthropic/claude-sonnet-4-6 routed directly via the Anthropic provider (no gateway proxy). No per-agent model overrides relevant to this issue. CLI failure occurs before any model interaction.

Logs, screenshots, and evidence

# --version works:
$ node dist/index.js --version
OpenClaw 2026.4.5

# All other subcommands SIGTERM after ~10s with no output:
$ node dist/index.js gateway status --json --no-probe  → SIGTERM
$ node dist/index.js gateway probe --json --timeout 2000 → SIGTERM
$ node dist/index.js config get gateway.mode           → SIGTERM

# OPENCLAW env vars:
OPENCLAW_GATEWAY_PORT=18789
OPENCLAW_NO_RESPAWN=1
OPENCLAW_CLI=1
OPENCLAW_SHELL=exec
OPENCLAW_BUNDLED_PLUGINS_DIR=/app/extensions
OPENCLAW_PATH_BOOTSTRAPPED=1

Impact and severity

• Affected: Any Docker-based OpenClaw deployment on 2026.4.5 • Severity: Medium — blocks all CLI-based management and inspection; gateway itself remains operational • Frequency: 100% reproducible (every CLI subcommand beyond --version) • Consequence: Cannot use openclaw CLI for status checks, cron management, config inspection, or diagnostics from within the container

Additional information

Last known good: 2026.4.2 (CLI functioned normally) First known bad: 2026.4.5 OPENCLAW_NO_RESPAWN=1 confirmed set with no effect. OPENCLAW_CLI=1 and OPENCLAW_SHELL=exec present in env. Browser control server listening on 127.0.0.1:18791. Gateway fully functional throughout (Telegram, cron, web dashboard all operational).