Docker Image Variant v2

[shyim]

I would like to do some breaking changes to the docker image. To not break current setups we should start with image versioning.

Example (taken from https://github.com/pimcore/docker#versioning):

• ghcr.io/shopware/docker-base:8.3-frankenphp (current)
• ghcr.io/shopware/docker-base:8.3-frankenphp-v2025.1 (current)
• ghcr.io/shopware/docker-base:8.3-frankenphp-v2026.1 (new one)

We deprecate the old image to time X and annoy people to upgrade to the new one. After the period the image tag without the explict versioning roll over to the next one.

Suggested changes to v2:

• Use Debian based Images because of musl performance issues and using official Node packages
• Reduce variation to just: FrankenPHP and this contains always GRPC / OpenTelemetry to keep it simple
• Remove all Shopware related env variables so they can be overwritten by .env file. https://github.com/shopware/docker/blob/main/fpm/Dockerfile#L27

My suggested images would be:

Production:

• ghcr.io/shopware/docker-base:8.3-frankenphp-v2026.1
  Development
• ghcr.io/shopware/docker-dev:8.3-node22-v2026.1
• ghcr.io/shopware/docker-dev:8.3-node24-v2026.1

[philipreinken]

Since we can't reliably reach everyone deploying the images, I don't see any real alternative either; so +1 for adding a monthly (or any other versioning scheme) tag suffix.

Use Debian based Images because of musl performance issues and using official Node packages

I like it - the size difference between alpine and debian-slim shouldn't matter too much.

Reduce variation to just: Caddy+PHP-FPM / FrankenPHP and this contains always GRPC / OpenTelemetry to keep it simple

Always bundling grpc and otel makes sense I think, but I'd reconsider dropping the default nginx variant, as I'd assume this is the go-to variant for anyone new to this image, setup and/or Shopware.

[philipreinken]

Remove all Shopware related env variables so they can be overwritten by .env file.

Not sure if I understand correctly - if this is regarding the app reading a .env file on its own, I'd expect this mechanism to be deactivated for the container images. SSOT should be the env variables set on the container IMO.