update php version on webdevops/php:8.2 image about dockerfile HOT 5 OPEN

The image for 8.2 is based on php:8.2-fpm-buster and this version contains only 8.2.7.
We would need to upgrade the base image to be bookworm. But as this is a heavy breaking change for everybody who is using and extending the 8.2 image, I'm not sure if this should be done.

from dockerfile.

In my imagination a 8.2 should always be the newest 8.2 version. if someones needs the the buster version they could use 8.2-buster.
in 8.2-alpine the version is bumped to 8.2.14 why not on 8.2?

from dockerfile.

We're not responsible for the underlaying PHP version. We just enhance the official PHP images. We've built the image webdevops/php:8.2 based on php:8.2-fpm-buster. So buster is the underlaying Linux distro and changing that while keeping the same image tag would be a major breaking change for a lot of people.

from dockerfile.

Maybe it would be a good idea to build webdevops/php:8.2 based on php:8.2-fpm and not php:8.2-fpm-buster because if the underlying distro of php:8.2-fpm changes it would be useful that the webdevops/php:8.2 also changes the distro.

from dockerfile.

We've built the image webdevops/php:8.2 based on php:8.2-fpm-buster. So buster is the underlaying Linux distro and changing that while keeping the same image tag would be a major breaking change for a lot of people.

They no longer update php:8.x-fpm-buster images since June 2023 ( Link to PR ). They added new LTS versions instead (php:8.x-fpm-bookworm). That way webdevops/php:8.2 stuck on PHP v8.2.7 and no longer get any PHP security updates.
I completely agree, it would be a breaking change to start using the new Debian LTS version. To resolve this we could probably use new tags for the images, something like webdevops/php-fpm-bookworm:8.2. But I guess it will take a lot of work to adapt everything to the new LTS version :(

from dockerfile.