Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Docker/Unraid: 2026.4.24 and 2026.4.25 gateway never becomes healthy; doctor --fix does not recover, 2026.4.26 doctor still hangs [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#73846•Fetched 2026-04-29 06:14:17
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
miguelariosmiguelarios
Participants
clawsweeper[bot]clawsweeper[bot]miguelariosmiguelarios
Timeline (top)
commented ×1cross-referenced ×1

On Docker/Unraid, OpenClaw 2026.4.24 and 2026.4.25 never bring the gateway up. Docker reports the container as unhealthy, but this is not just a Docker healthcheck false positive: /healthz never reports healthy and the gateway does not become usable.

I waited a long time for the gateway to finish starting, but it never came up. Running openclaw doctor --fix did not recover the instance.

I also tested [email protected] directly. doctor --fix improved the bundled dependency install logging and successfully installed missing bundled plugin runtime deps, but after that it stopped producing output and remained stuck as an orphaned openclaw-doctor process. SIGTERM did not stop it; SIGKILL was required.

Error Message

  • fail with a clear actionable error.

Root Cause

On Docker/Unraid, OpenClaw 2026.4.24 and 2026.4.25 never bring the gateway up. Docker reports the container as unhealthy, but this is not just a Docker healthcheck false positive: /healthz never reports healthy and the gateway does not become usable.

I waited a long time for the gateway to finish starting, but it never came up. Running openclaw doctor --fix did not recover the instance.

I also tested [email protected] directly. doctor --fix improved the bundled dependency install logging and successfully installed missing bundled plugin runtime deps, but after that it stopped producing output and remained stuck as an orphaned openclaw-doctor process. SIGTERM did not stop it; SIGKILL was required.

Code Example

curl -fsS http://127.0.0.1:18789/healthz

---

openclaw doctor --fix

---

timeout 240s npx -y openclaw@2026.4.26 --version
   timeout 240s npx -y openclaw@2026.4.26 doctor --fix

---

OpenClaw 2026.4.26 (be8c246)

Bundled plugin runtime deps are missing.
...
Installing bundled plugin runtime deps...
Still installing bundled plugin runtime deps after 15s...
Still installing bundled plugin runtime deps after 30s...
Still installing bundled plugin runtime deps after 45s...
Installed bundled plugin runtime deps in 51s
...

---

openclaw-doctor
RAW_BUFFERClick to expand / collapse

Bug type

Crash / startup failure / doctor repair failure

Summary

On Docker/Unraid, OpenClaw 2026.4.24 and 2026.4.25 never bring the gateway up. Docker reports the container as unhealthy, but this is not just a Docker healthcheck false positive: /healthz never reports healthy and the gateway does not become usable.

I waited a long time for the gateway to finish starting, but it never came up. Running openclaw doctor --fix did not recover the instance.

I also tested [email protected] directly. doctor --fix improved the bundled dependency install logging and successfully installed missing bundled plugin runtime deps, but after that it stopped producing output and remained stuck as an orphaned openclaw-doctor process. SIGTERM did not stop it; SIGKILL was required.

Environment

  • OpenClaw versions tested:
  • Install/deployment method: Docker
  • Host OS: Unraid
  • Runtime inside container:
    • Linux x64
    • Node v24.14.0
  • Gateway command pattern:
    • openclaw gateway --allow-unconfigured --bind lan --port 18789

Steps to reproduce

  1. Run OpenClaw in Docker/Unraid using 2026.4.24 or 2026.4.25.
  2. Start the gateway container.
  3. Wait for the gateway to become healthy.
  4. Check Docker health status.
  5. Check gateway health endpoint inside the container: 
    curl -fsS http://127.0.0.1:18789/healthz
  6. Run: 
    openclaw doctor --fix
  7. Observe that doctor does not recover the gateway.
  8. Separately test 2026.4.26: 
    timeout 240s npx -y [email protected] --version
timeout 240s npx -y [email protected] doctor --fix

Expected behavior

  • Gateway should start successfully in Docker.
  • /healthz should return healthy once startup completes.
  • Docker should report the container as healthy.
  • openclaw doctor --fix should either:
    • repair the instance and exit cleanly, or
    • fail with a clear actionable error.
  • doctor --fix should not hang indefinitely or leave orphaned openclaw-doctor processes.

Actual behavior

For 2026.4.24 and 2026.4.25:

  • Gateway never becomes usable.
  • Docker reports the container as unhealthy.
  • /healthz does not report healthy.
  • Waiting longer does not resolve it.
  • Running openclaw doctor --fix does not recover the gateway.

For 2026.4.26 (be8c246):

  • doctor --fix starts and installs missing bundled plugin runtime deps.
  • Install completes successfully.
  • After the bundled deps install step, doctor stops producing output and does not exit.
  • Process remains alive as openclaw-doctor.
  • SIGTERM does not stop it.
  • SIGKILL is required.

Observed 2026.4.26 output included:

OpenClaw 2026.4.26 (be8c246)

Bundled plugin runtime deps are missing.
...
Installing bundled plugin runtime deps...
Still installing bundled plugin runtime deps after 15s...
Still installing bundled plugin runtime deps after 30s...
Still installing bundled plugin runtime deps after 45s...
Installed bundled plugin runtime deps in 51s
...

After that, no further output was produced and the process remained running.

Process check showed an orphaned doctor process similar to:

openclaw-doctor

Additional context

This looks related to the bundled plugin runtime deps / plugin loader regressions around the 2026.4.24 to 2026.4.26 releases, but the exact Docker/Unraid failure mode does not appear to be fully covered by the existing issues I found.

Possibly related:

  • #72042, 2026.4.24 gateway startup fails after update, missing dist files
  • #71986, 2026.4.24 update causes doctor/plugin install loop and gateway crashing
  • #72114, bundled runtime deps staging timeout leaves gateway/deps inconsistent
  • #72775, doctor lacks streamed progress during bundled deps install
  • #72779, doctor reports success but deps land outside expected bucket
  • #73454, 2026.4.26 regression, startup degradation after bundled deps fix
  • #73532, plugin loader/runtime-deps hot loop starving gateway
  • #62850 is adjacent but not the same issue, since this is not merely Docker reporting unhealthy while /healthz works. In this case /healthz does not become healthy and the gateway does not come up.

Impact

This blocks Docker/Unraid deployments from upgrading past 2026.4.23. The gateway never becomes available on 2026.4.24 and 2026.4.25, and the repair path via doctor --fix does not recover the instance. Testing 2026.4.26 shows doctor still hanging after the bundled deps repair step.

extent analysis

TL;DR

The issue can be potentially resolved by investigating the bundled plugin runtime dependencies installation process and the doctor's behavior in the 2026.4.26 version.

Guidance

  1. Investigate the installation of bundled plugin runtime dependencies: The output from 2026.4.26 suggests that the installation of these dependencies completes successfully, but the process then hangs. Understanding what happens after this step could provide insights into the issue.
  2. Analyze the doctor's behavior: The fact that doctor --fix stops producing output and remains running as an orphaned process indicates a potential issue with the doctor's implementation or its interaction with the environment.
  3. Compare with related issues: Reviewing the related issues mentioned (e.g., #72042, #71986, #72114) might provide clues or workarounds that could be applied to this specific problem.
  4. Test with additional logging or debugging: Enabling more verbose logging or using debugging tools might help identify what causes the doctor to hang and why the gateway does not become healthy.

Example

No specific code snippet can be provided without more context on the implementation details of OpenClaw and its doctor command. However, adding logging statements or using a debugger to step through the code around the bundled plugin runtime dependencies installation and the doctor's fix process could be beneficial.

Notes

The issue seems to be related to changes introduced around the 2026.4.24 to 2026.4.26 releases, particularly with how bundled plugin runtime dependencies are handled. The behavior observed in 2026.4.26 suggests a regression or an incomplete fix.

Recommendation

Apply workaround: Given the issues observed with 2026.4.24, 2026.4.25, and the hanging behavior in 2026.4.26, it might be necessary to wait for a future release that addresses these problems or to find a specific

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

  • Gateway should start successfully in Docker.
  • /healthz should return healthy once startup completes.
  • Docker should report the container as healthy.
  • openclaw doctor --fix should either:
    • repair the instance and exit cleanly, or
    • fail with a clear actionable error.
  • doctor --fix should not hang indefinitely or leave orphaned openclaw-doctor processes.
#GPU compatibility#latency issue#model loading#dependency error#configuration error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Docker/Unraid: 2026.4.24 and 2026.4.25 gateway never becomes healthy; doctor --fix does not recover, 2026.4.26 doctor still hangs [1 comments, 2 participants]