# PHP Images > Use this skill when working with Specsnl PHP Docker images. It covers what the images are, their repository structure and variants, which PHP versions are maintained, and how to locate sibling images both on GitHub and locally. - Skill: `specsnl/php-images` (Agent Skill) - Install (CLI): `npx skillmds@latest add specsnl/php-images` - Raw SKILL.md: https://api.skillmd.com/api/skills/specsnl/php-images/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: DevOps & Infra - Author: specsnl (https://skillmd.com/u/specsnl) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/specsnl/php-images --- # PHP Images Skill This skill provides information about the PHP images used in the Specsnl projects, including where to find the source files and how to locate sibling images for other PHP versions. ## What are the PHP images? The PHP images are Docker images that serve as the base for the various PHP environments used in Specsnl projects. These images are built on top of official PHP images and include additional dependencies and configurations specific to our needs. Each PHP image repository follows a consistent structure with three main Dockerfiles (variants): - `fpm/Dockerfile`: The Dockerfile for the FPM variant of the image. - `apache/Dockerfile`: The Dockerfile for the Apache variant of the image. - `frankenphp/Dockerfile`: The Dockerfile for the FrankenPHP variant of the image. Furthermore, there is a `files` directory that contains additional files used during the build process, such as configuration files and scripts. - `files/general`: Contains files that are shared across all PHP Dockerfiles. - `files/`: Contains files specific to the `` variant of the image. ## Supported PHP versions Specsnl maintains images for 3 supported PHP versions at any given time. To determine the current supported versions, fetch the endoflife.date API: `https://endoflife.date/api/v1/products/php/`. This returns a JSON array of PHP releases with their active-support and security-support end dates. Use the 3 most recent versions that have not yet reached end-of-life as the supported set. If a Specsnl repository for the newest PHP version does not exist yet, we are still supporting the previous version as the latest one. For example, if PHP 8.5 is the newest version but the `php85` repository has not been created yet, we are still treating PHP 8.4 as the latest. ## Where can I find the source files on GitHub? The source files for the PHP images can be found in the repositories that follow the following structure: `https://github.com/specsnl/php`. For example, for PHP 8.5, the source files are located in `https://github.com/specsnl/php85`. ## How are the published images named and tagged? The built images are published to the GitHub Container Registry (GHCR). The current (newer) naming scheme encodes the variant and build target as path segments under the repository, and uses the tag only for the version: `ghcr.io/specsnl/php[/][/]:` - ``: omitted for the FPM variant; otherwise `apache` or `frankenphp`. - ``: omitted for the `runtime` (production) target; otherwise `builder` (adds development tooling such as Composer and Xdebug) or `builder_nodejs` (builder plus Node.js). - ``: `latest`, a release tag (e.g. `0.5.5`), `main`, or `pr-`. Examples for PHP 8.5: ```bash docker pull ghcr.io/specsnl/php85:latest # fpm runtime docker pull ghcr.io/specsnl/php85/builder:latest # fpm builder docker pull ghcr.io/specsnl/php85/builder_nodejs:latest # fpm builder + Node.js docker pull ghcr.io/specsnl/php85/apache:latest # apache runtime docker pull ghcr.io/specsnl/php85/apache/builder:latest # apache builder docker pull ghcr.io/specsnl/php85/frankenphp:latest # frankenphp runtime docker pull ghcr.io/specsnl/php85/frankenphp/builder:latest # frankenphp builder ``` ### Legacy naming scheme (older) Older images encoded the variant/target **and** the version together in the tag, joined with dashes, instead of as path segments: `ghcr.io/specsnl/php:--` For example, the legacy `ghcr.io/specsnl/php85:builder-latest` is equivalent to the new `ghcr.io/specsnl/php85/builder:latest`. Both forms may still be encountered in the wild, but the **path-segment scheme is the newer, preferred one**. When you come across the legacy dash-in-tag form, treat it as the older convention and migrate it to the new path-segment form: move the variant/target segments out of the tag into the image path, leaving only the version (e.g. `latest`) as the tag. ### Legacy vendor (older) The images used to be published under the `ilyes512` vendor before moving to `specsnl`. The correct, current vendor is **`specsnl`**. These older `ilyes512`-vendored images predate the path-segment scheme, so they use the legacy dash-in-tag naming — for example `ghcr.io/ilyes512/php85:builder-latest`. When you encounter such a reference, migrate it in-place to **both** the current vendor and the new path-segment scheme: `ghcr.io/ilyes512/php85:builder-latest` becomes `ghcr.io/specsnl/php85/builder:latest`. ## How to find sibling images on GitHub The sibling repositories follow the same URL pattern described above. For example, if you are looking at the `php85` repository, the siblings are at `https://github.com/specsnl/php84` and `https://github.com/specsnl/php83`. ## How to find sibling images locally If you are working locally in one of the PHP image repositories and want to find the sibling images for other PHP versions, check if there are sibling directories in the same parent directory. For example, if you are in the `php85` repository, check if `php84` and `php83` directories exist alongside it. If they do, they are most likely the sibling images for PHP 8.4 and PHP 8.3 respectively. Verify by checking the remote repository URLs in the git configuration or by reading the README files in those directories.