Skip to content

Upgrade Docker base image from Debian bookworm to trixie #2826

@curtismchale

Description

@curtismchale

Builds

Goal

Upgrade the wp-proudcity Docker base image from Debian bookworm (12) to trixie (13).

Background

Split out from #2824 (PHP 8.3 upgrade). We deliberately kept the OS pinned to bookworm on that ticket so the PHP bump could be isolated. This is the follow-up to do the OS bump on its own.

Target tag: php:8.3-apache-trixie.

Why separate

Bumping PHP and Debian together means any production regression has two suspects. Doing them in sequence keeps each change debuggable.

Acceptance

  • Dockerfile FROM updated to php:8.3-apache-trixie.
  • Image builds cleanly.
  • All apt packages still install (package names sometimes change across Debian majors — libcurl4-openssl-dev, libmcrypt-dev, mariadb-client, etc.).
  • All PHP extensions still load (gd, mysqli, opcache, bcmath, redis, mcrypt).
  • WP admin loads in staging, golden-path smoke test passes.

Risks to watch

  • Debian trixie ships newer OpenSSL/libcurl — check anything that pins to specific TLS behavior.
  • mariadb-client major version changes; verify wp-cli db commands still work.
  • Any pecl extensions compiled against bookworm system libs need rebuild — handled automatically by the image build, but worth confirming.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions