install_workerman3524_base_docker.sh

Compatibility and limits

• Requires Linux with systemd, Docker build support, root, writable /data and the selected free host port (2345 by default). This is a legacy Workerman 3.5.24/PHP 7.2 compatibility example; PHP 7.2 is unsupported.
• Accepts --data-dir, --container-name and --port. No dry-run, backup or automatic rollback. php:7.2-cli and composer:2.2 are mutable upstream tags. The generated Dockerfile disables archive metadata expiry checks and allows insecure APT repositories inside the image build.
• Only composer.json is copied before composer install, so a host composer.lock does not pin that installation stage. An existing composer.json is retained and can change the requested Workerman version. Re-check dependencies when upstream bytes change.

Files, services, and data affected

• Creates /data/workerman3.5.24/app and logs; writes app/start.php and composer.json only if absent. Overwrites DATA_DIR/Dockerfile on every run without a backup, including custom edits.
• Builds helper-workerman:3.5.24 first, then force-removes a same-name container and starts its replacement with the chosen host port mapped to container 2345. Only logs is bind-mounted; application files are copied into the image. Host app edits require a rebuild and replacement.
• Reuses host files without backup. A mounted logs directory does not ensure custom application logging writes there. No TLS or public access restriction is configured.

Read-only verification

• Substitute custom names/paths if used. Inspect `docker inspect workerman3524 --format '{{json .Mounts}} {{json .HostConfig.PortBindings}}'`, `docker ps --filter name=workerman3524`, and `docker logs --tail 100 workerman3524`.
• Check `docker exec workerman3524 php -v` and `docker exec workerman3524 composer show workerman/workerman` for the actual runtime and installed package version.
• For the unchanged sample, verify its loopback HTTP response separately. A successful curl status is not application validation; custom request handlers need their own reviewed checks. The script warns and still prints completion when HTTP readiness fails or curl is missing.

If it fails

A build failure occurs before the old named container is removed, but Dockerfile may already be overwritten. Preserve host files and existing image/container evidence; inspect dependency and archive errors. After replacement failure, check port conflicts, image version and logs before another rebuild. Back up custom Dockerfile and app files; the script cannot restore the previous container automatically.

PHP · Composer

Download, inspect, then verify the version before execution. A hash only identifies these exact bytes; it does not prove safety. Piped commands run remote content immediately, and upstream dependencies can change.