Re: Docker images for 8.6 now default to ZTS

From: Date: Fri, 20 Nov 2026 23:28:57 +0000
Subject: Re: Docker images for 8.6 now default to ZTS
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-133160@lists.php.net to get a copy of this message
Am 20.11.2026, 12:23:15 schrieb Matteo Beccati <php@beccati.com>: > Hi, > > I've been mentioned in: > > 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/1689 > > > Cheers > -- > Matteo Beccati > Hi 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. ZTS is not really an experiment at this point, FrankenPHP is stable for 3 years now. Running FPM with ZTS does nothing in terms of actually threading. Marc’s recent changes makes the overhead minimal and there is more work to reduce that even more. The benchmarks on this issue are all mostly bogus and with wrong assumptions. I don’t see Marcs initial post as a request from PHP, and he was pretty open that this is not an upstream fact yet. 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. 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

« previous php.internals (#133160) next »