Solution

Workerman says completed but HTTP readiness failed

Separate build, container startup, the optional curl probe and application validation before another replacement.

Updated 2026-10-30

Problem statement

Does the completion banner prove the application is healthy?

No. The script builds first, replaces the named container, then retries a loopback HTTP probe only if curl exists. Failure produces a warning and execution continues to the completion banner. Missing curl also prevents the probe from passing.

Preserve files and the current image/container evidence; inspect docker ps, logs, port publication and the actual package version. Review the unchanged sample response separately from custom business checks. This PHP 7.2/archive build is a legacy compatibility example with mutable dependencies and no automatic rollback.

What to check

  • docker ps --filter name=workerman3524
  • docker logs --tail 100 workerman3524
  • docker inspect workerman3524 --format '{{json .HostConfig.PortBindings}}'

Parent topic

Use PHP 7.2 and Workerman 3.5.24 examples for inherited compatibility work with an upgrade plan.