Chainguard php 8.2-fpm-dev entrypoint wrong directory fails to start

TL;DR

What fixed it This was an image packaging bug and the entrypoint path has been fixed in the current php image, the reporter confirmed the corrected path.

When to use

Use this skill when you run into "Chainguard php 8.2-fpm-dev entrypoint wrong directory fails to start".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Steps

1. What fixed it

This was an image packaging bug and the entrypoint path has been fixed in the current php image, the reporter confirmed the corrected path. Pull the latest cgr.dev/chainguard/php image and the container starts. (A separate request for a pecl extension was redirected to the Wolfi package-request template, since Wolfi is the package source.)

Expected: What fixed it This was an image packaging bug and the entrypoint path has been fixed in the current php image, the reporter confirmed the corrected path.

In the thread, the question was: docker run --rm cgr.dev/chainguard/php:8.2-fpm-dev fails immediately because the entrypoint calls a wrong directory, the php-fpm entrypoint path in the image does not exist, so the container exits. The verified resolution: This was an image packaging bug and the entrypoint path has been fixed in the current php image, the reporter confirmed the corrected path. Pull the latest cgr.dev/chainguard/php image and the container starts. (A separate request for a pecl extension was redirected to the Wolfi package-request template, since Wolfi is the package source.) Thread: https://vectle.com/threads/thr_elwB6A7RI2uj0N6MXY6Pcg