Minimal PHP Docker image for wordpress based on kooldev/php. It's use is intended for kool.dev, but can fit in any other PHP use-case.
Previously supported but now deprecated tags: 8.3, 8.3-prod, 8.2, 8.2-prod, 8.1, 8.1-prod, 8.0, 8.0-prod, 7.4, 7.4-prod, 7.4-nginx, 7.4-nginx-prod, 8.0-nginx, 8.0-nginx-prod.
Check kooldev/php to see available options.
CI rebuilds on docker-php-updated repository dispatches after PHP parent
publication, relying on the PHP parent's scheduled rebuild rather than a separate
WordPress schedule. Push, pull request, and manual runs remain available.
Native AMD64 and ARM64 jobs each build once with fresh parent stages and run the
PHP, WP-CLI, NGINX, Supervisor, and WordPress checks on that same local image.
Dispatch delivery does not guarantee a successful downstream build;
check the CI/CD run before treating published tags as refreshed.
Only non-PR runs on this repository's master can log in or publish. After all
checks in each native job pass, it pushes the tested image to a staging tag:
ci-docker-wordpress-<run_id>-<run_attempt>-<variant>-<arch>. Run/attempt-scoped artifacts
record the staging tag, locally verified Linux architecture/image ID, and immutable repository digest. PRs, forks,
and manual feature-branch runs only build and test.
After all 16 native jobs succeed, publication validates all eight AMD64/ARM64 pairs and their tested local platform/image-ID records before changing any stable tag. Stable manifests reference those exact tested digests; publication never rebuilds. Publication trusts the complete staging artifacts rather than performing 32 redundant remote inspections. Manifest assembly still reads Docker Hub, so its pull quota can still apply. The publisher uses the Docker driver, avoiding an extra BuildKit container image pull.
If a run partially fails, rerun the entire workflow, not just failed jobs: artifacts from earlier attempts are intentionally excluded. Registry updates to eight tags are not atomic; if promotion fails midway, rerun the entire workflow to refresh the complete set. Staging tags are not public compatibility tags.
CI uses shared Bash/jq actions,
pinned in the workflow. Release tests live there; WordPress generation and native
runtime checks stay here.
The existing PHP 8.1 tags are retained, but PHP 8.1 is end-of-life and its Kool parent is no longer rebuilt by docker-php. Rebuilding WordPress cannot patch an unmaintained parent; use a maintained PHP tag.
You should change fwd-template.json for configuration and template folder for the actual base templates.
After any changes, we need to run kool run template to parse the templates and generate all versions folder/files.