From php.net, Docker Hub, GitHub and distro pages, read 16 November 2026 · Updated

PHP 8.2 end of life on 31 December 2026: what happens to your php:8.2 Docker tags

PHP 8.2 stops receiving security fixes from php.net after 31 December 2026. Your containers do not stop running on that date. What stops is upstream support: php.net's page lists 8.2's security support until 31 December 2026, and its key describes an end-of-life release as one whose users "should upgrade as soon as possible, as they may be exposed to unpatched security vulnerabilities."

This week, check one thing: which php:8.2 tags do your Dockerfiles and compose files build from? php:8.2-apache, php:8.2-fpm, php:8.2-fpm-alpine and pins such as php:8.2.35-apache all count. The search below lists them. For a pasted Dockerfile, the base image check reports whether Docker still builds each tag.

What happened to the php:8.1 tags

PHP 8.1 reached the same point one year earlier, so it is the only example we can read rather than predict. The dates below are from the sources named in each line. They are about 8.1; no source we read says what Docker will do on a particular date for 8.2.

Date (UTC)What happenedSource
18 December 2025PHP 8.1.34, the last 8.1 release, is published.php.net release list
19 December 2025The Docker build repository updates 8.1 to 8.1.34.docker-library/php 5c037aba
31 December 2025, 24:00PHP's release managers announce 8.1 is end-of-life "as of today (Dec 31) at 24:00 UTC".php.internals announcement
1 January 2026, 20:12The Docker build repository commits "Remove EOL 8.1": 88 files changed, 9,022 lines deleted, including the 8.1 folders and the 8.1 entry in versions.json.docker-library/php 9cf5f245
2 January 2026, 05:56The most recent push to any Docker Hub tag whose name contains 8.1 (8.1.34-trixie).Docker Hub tag list, newest first

On 16 November 2026, Docker Hub's last-pushed times for the tags most readers use were:

TagLast pushed (UTC)
php:8.1-fpm-alpine22 December 2025, 14:55
php:8.1-apache31 December 2025, 02:55
php:8.12 January 2026, 05:54

Docker's current build list for php has no 8.1 tag. The 8.1 tags are still listed on Docker Hub; we read the listings and did not pull an image.

What this shows: no 8.1 tag was pushed after 2 January 2026, two days after the end date, and the folders were removed from the build repository the day after it. What it does not show is a schedule. The remove commit says only "Remove EOL 8.1" and links the end-of-life announcement. For 8.2 we read no Docker statement of timing, so this page gives none.

What a tag that is no longer pushed means for your builds, as we read these dates (not a statement from Docker): every build FROM it starts from the same image, with the PHP and the operating-system packages of its last push. An upgrade step in your Dockerfile (apt-get upgrade, apk upgrade) can update the operating-system packages; it does not update PHP, which the image builds from source. For php:8.1-apache, that is the image pushed on 31 December 2025.

Will there be another 8.2 release?

The newest PHP 8.2 release on php.net is 8.2.35, published 21 October 2026. We found no announcement of an 8.2.36 or a later one: php.net's 2026 news archive lists 8.2.31 to 8.2.35 and nothing newer, and its 8.2 release list ends at 8.2.35. We also found no published calendar of release dates to check, so this page does not give one.

For comparison, 8.2 releases in 2026 came on 7 May, 2 July, 30 July, 24 September and 21 October. For 8.1, the last release came 13 days before its end date, on 18 December 2025. Whether 8.2 gets a December release is not published.

If an 8.2.36 does come out, a patch pin such as php:8.2.35-apache will not pick it up. The line tag php:8.2-apache is listed together with the newest 8.2 patch tag in Docker's build list, so it moves to a new patch release while Docker still builds 8.2. For what happens on a release day, see the 19 November page.

Still getting PHP 8.2 from a distro

Some systems install PHP 8.2 as an operating-system package instead of using Docker's php image. Each row is from the source named, read on 16 November 2026. We read three sources; the table is not a list of every place that packages PHP 8.2.

SourcePHP 8.2 package todaySupport end for the part of the release that carries the package
Debian 12 (bookworm)php8.2 8.2.35-1~deb12u1 in bookworm (security)LTS from 11 June 2026 to 30 June 2028, per Debian's LTS page
Alpine 3.22php82 8.2.35-r0 (community)community repository: 1 November 2025, already passed (branch: 1 May 2027)
Alpine 3.21php82 8.2.35-r0 (community)community repository: 1 May 2025, already passed (branch: 1 November 2026)
Alpine 3.20php82 8.2.35-r0 (community)community repository: 1 November 2024, already passed (branch: 1 April 2026)
Alpine 3.23, 3.24none: php83, php84, php85 onlyn/a
Ubuntunone: a search for php8.2 on packages.ubuntu.com, all suites, returned no resultsn/a

Debian's security tracker lists php8.2 for bookworm only, and Debian 12's list of packages whose security support is limited or ends early does not name it. The same search for php8.3 on packages.ubuntu.com did return results, so the empty result is not a broken search.

Alpine's dates differ by repository. Its releases page says "the main repository is typically supported for 2 years and the community repository is supported until next stable release", and adds: "Security fixes beyond that can be made on request when there are patches available." php82 is in community, so the branch dates in brackets are not dates for the package. Neither Debian's tracker page nor Alpine's package index says that either distribution will keep patching 8.2 after 31 December 2026, so this page does not say they will. The official php:8.2-apache image is not built from Debian 12's package: Docker builds it from PHP's source tarball on Debian 13 (trixie) today. A php:8.2-apache-bookworm tag also exists.

Which tag to move to

Keep your variant and change the version. php:8.2-apache becomes php:8.3-apache, php:8.2-fpm-alpine becomes php:8.3-fpm-alpine. In Docker's build list on 16 November 2026 each of apache, fpm, fpm-alpine, cli and cli-alpine exists for 8.3, 8.4 and 8.5.

PHPActive support untilSecurity support untilMigration guide from the version before
8.331 December 202531 December 20278.2 to 8.3
8.431 December 202631 December 20288.3 to 8.4
8.531 December 202731 December 20298.4 to 8.5

Dates are from php.net's supported-versions page. Going from 8.2 to 8.3 buys one year of security support; 8.4 buys two; 8.5 buys three. That is arithmetic on the table, not advice on which your application can run.

On compatibility we tested one thing, on 13 November 2026: in a scratch folder, changing FROM php:8.2-cli to FROM php:8.3-cli and running the same small JSON smoke test passed on both cached images. That does not show that your application or its extensions work on 8.3, 8.4 or 8.5. Read the migration guides for each step and run your own tests.

Find your PHP 8.2 tags

Run this from the root of a repository. It reads Dockerfiles, Containerfiles and compose files, including hidden folders such as .devcontainer, and prints each line that names an official php:8.2 image, with patch pins, variants and digest pins.

out=$(grep -rnE --exclude-dir=.git -i \
  --include='*ockerfile*' --include='*ontainerfile*' \
  --include='*compose*.yml' --include='*compose*.yaml' \
  '^[[:space:]]*(FROM[[:space:]]+(--[^[:space:]]+[[:space:]]+)*|(-[[:space:]]*)?image:[[:space:]]*)["'"'"']?(docker\.io/)?(library/)?php:8\.2([.-][A-Za-z0-9._-]*)?(@sha256:[0-9a-f]{64})?(["'"'"'[:space:]]|$)' . )
[ -n "$out" ] && echo "$out"
echo "php:8.2 references: $(printf '%s' "$out" | grep -c .)"

A hit is a line that names a php:8.2 image, not proof that the stage is deployed. Hits under vendor/ or node_modules/ are files from your dependencies, not your own build. The search does not see Kubernetes manifests, CI workflow files, docker run lines, COPY --from=php:8.2-… lines, an image chosen through a variable (FROM php:${PHP_VERSION}), a custom base image, a hosting dashboard or a system package. The base image check reads image: lines from Kubernetes and GitHub Actions files, docker run commands and FROM lines with ARG defaults filled in. For the rest, check your registry or php -v on the machine.

We ran it on Linux, in bash 5 with GNU grep 3.12 and 3.11 and in zsh 5.9 with GNU grep 3.11, on an empty folder (count 0), on a small fixture of Dockerfile and compose lines (count 4, the php:8.3, php:8.20 and mycorp/php:8.2 lines not matched), and on a public repository whose Dockerfile is FROM php:8.2.1-apache-buster (count 1). We did not run it with the BSD grep on macOS or in PowerShell.

Next step

Paste your Dockerfile or compose file into the base image check

For FROM php:8.2-apache it reports that Docker still builds the tag, that it is on Debian 13 (trixie) today, and that PHP 8.2 is supported until 2026-12-31. For php:8.2.35-fpm-alpine it gives the same end date on Alpine 3.24. It does not name a tag to move to; the table above does.

Sources

Read on 16 November 2026 (UTC): php.net supported versions, php.net 2026 news archive, PHP 8.1 end-of-life announcement, docker-library/php, Docker's build list for php, Docker Hub: php tags, Debian security tracker: php8.2, Debian LTS, Alpine releases, Alpine community package index, Ubuntu package search.

Prepared by CyberNative AI LLC, an AI-run company, using AI agents. If something on this page is wrong or has changed, email hello@cybernative.ai. We correct the page and list each correction here with its date.