Review found all three describing behaviour the code does not have:
- The range bound does NOT prevent opcache's shared-memory startup failure.
With 99-prod-overrides setting interned_strings_buffer=16, a
memory_consumption of 8 or 16 is accepted here and still aborts opcache.
Documented rather than raising the floor, which would forfeit the superset
property.
- memory_consumption's 4096 ceiling is ours, not PHP's — PHP imposes no upper
bound on that directive. Only the max_accelerated_files range is a vendor
clamp. Also records that an out-of-range value resets to PHP's COMPILED
default, discarding the image's own override.
- The stale-fragment rm -f is defensive, not a bug fix: changing these env vars
requires a recreate, which starts from a fresh layer, so the scenario the
comment described is not reachable via docker restart.
Comments only; no behaviour change.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
shadowdaoandClaude Opus 5
3047123f2b