Re: Docker images for 8.6 now default to ZTS
| From: | Marc Henderkes | Date: | Sat, 21 Nov 2026 05:19:40 +0000 |
| Subject: | Re: Docker images for 8.6 now default to ZTS | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-133163@lists.php.net to get a copy of this message | ||
On 21/11/2026 06:28, Benjamin Außenhofer wrote:
Am 20.11.2026, 12:23:15 schrieb Matteo Beccati <php@beccati.com>:Correct, aside from PHP not being in a position to "officially request" changes to Dockers official images, I think https://github.com/docker-library/php/issues/1673 should make it fairly clear that the maintainers didn't understand my question as "official". The idea to remove NTS entirely was raised by one of the maintainers and I stated: There are still some (very niche) functionalities that I've not made work in ZTS yet: the mm session backend, fuzzer SAPI (PR open), the discontinued imap extension (since 8.4), a few others. For all normal users the switch to ZTS should be completely fine. Also, both apache SAPIs build under ZTS, so that doesn't have to be dropped.Hi, I've been mentioned in: https://github.com/docker-library/php/issues/1719 <https://github.com/docker-library/php/issues/1719> and I became aware that all PHP docker images now are ZTS builds. It was suggested to do so and apparently the Docker team took it as an official request. Was it? If not, I'm not sure it was appropriate to experiment like this on such a large user base, before publishing an RFC, discussing it and voting. For reference: - https://github.com/docker-library/php/issues/1673 <https://github.com/docker-library/php/issues/1673> - https://github.com/docker-library/php/issues/1689 <https://github.com/docker-library/php/issues/1689> Cheers -- Matteo BeccatiHi Matteo, First, the Docker images are not an PHP project, so I don’t think an RFC is in the scope to change this. The „official“ part of these images is referencing that they are official docker images, not official PHP images.
The 1719 issue is from someone with an extension or application-server not written in PHP. PHP never ensured compatibility for extensions between minor versions. The argument with ZTS non-support by APM vendors I cannot get behind, Datadog, Blackfire, Tideways all support ZTS, NewRelic has a Beta but they are not compatible with 8.6 NTS yet either. The chdir argument is also not relevant, because its about extensions, which don’t have our backwards compatibility promise. Unfortunately, the arguments seem to have been put together without verifying what they actually mean. There's a severe misunderstanding going on in regards to how they relate to thread safety, their build issues, or what they even mean at all (re --disable-zend-signals). Their build failed because they accessed sapi_globals & co directly instead of going through the respective access macros, because they rely on --disable-zend-max-execution-timers cpu-time (see below) and on chdir() not resetting after a request. Like Benjamin said, none of these has ever been part of any BC promise to SAPIs or extensions and none of them is an architectural blocker why their server couldn't be compatible with ZTS.
The only thing that I see could be confusing for normal users of PHP is the max_execution_time / set_time_limit() cpu clock to wall time change.
greetings
Benjamin
Perhaps not the right place for this discussion, but I would implore anyone having an opinion on this to chime in at https://github.com/php/php-src/issues/25499. I don't really understand why zend execution timers have this effect in the first place - counting wall vs clock time isn't coupled to the thread safety model.
Sorry to everyone having to deal with this outcry
- Marc