php74-fpm and pcre error with composer if you install any extension

[phpdocker-io]

php74-fpm and pcre error with composer if you install any extension

[luispabon]

Workaround is in place, builds in progress:

https://github.com/phpdocker-io/base-images/actions/runs/1481517715

Apologies for the slow builds, I recently added arm32 and 64 builds which take some time.

[Danack]

@thisisablock your link didn't work for me - I guess https://bugs.php.net/bug.php?id=81424 is the relevant issue.

btw apparently adding a apt-get dist-upgrade -y && \ before the PHP install makes the issue go away.

[luispabon]

Ah, looks like there's also a new version if libpcre that is not getting installed with the other updates, hence the crash. Gonna kick off new builds now

[luispabon]

Thanks all for double checking. Closing this now

@tannoiser I personally avoid upgrades on containers because it makes builds non-reproducible, and due to the way layering works on images, container size can balloon. This is part of the reason why images are being built daily, instead of waiting for a new php release. In any case it's not inherently wrong - you do you.

[thisisablock]

its related to all new php updates which rely on a PCRE update / bugfix.
https://www.php.net/index.php#id2021-11-19-1

Our only way to fix this was to downgrade in the container. The image has nothing to do with this issue because its loading just the latest minor version of php.

apt-cache policy php7.4

choose an older version (for example php7.4 | 7.4.3-4ubuntu2.7)
and downgrade your whole php stack.

apt-get install php7.4=7.4.3-4ubuntu2.7 php7.4-cli=7.4.3-4ubuntu2.7 php7.4-common=7.4.3-4ubuntu2.7 php7.4-fpm=7.4.3-4ubuntu2.7 php7.4-json=7.4.3-4ubuntu2.7 php7.4-opcache=7.4.3-4ubuntu2.7 php7.4-readline=7.4.3-4ubuntu2.7 php7.4-json=7.4.3-4ubuntu2.7 php7.4-opcache=7.4.3-4ubuntu2.7 php7.4-curl=7.4.3-4ubuntu2.7 php7.4-gd=7.4.3-4ubuntu2.7 php7.4-intl=7.4.3-4ubuntu2.7 php7.4-mbstring=7.4.3-4ubuntu2.7 php7.4-mysql=7.4.3-4ubuntu2.7 php7.4-soap=7.4.3-4ubuntu2.7 php7.4-sqlite3=7.4.3-4ubuntu2.7 php7.4-xml=7.4.3-4ubuntu2.7 php7.4-zip=7.4.3-4ubuntu2.7

[thisisablock]

thanks luis! have a nice weekend

[mihitha]

Thanks @luispabon , It is working for me now. (7.4)

[cfroystad]

The problem seems related to oerdnj/deb.sury.org#1682

[luispabon]

Thanks for the report, I was just looking into it.

It indeed seems like an issue with php 7.4.26. The current build (last night) of our image is on 7.4.25 and .26 must've come out in the last few hours.

[thisisablock]

@luispabon

8.0.13, 7.4.26 and 7.3.33 are affected

[luispabon]

@thisisablock I can't reproduce it on 7.3.33, but indeed on the others.

[thisisablock]

@luispabon can confirm - 7.3.33 is safe

[luispabon]

Unfortunately the new build won't fix the problem as it stands as libpcre isn't being updated. I reckon and I've said as much on the ondrej repo's issue above that the php packages should directly depend on this newer version of pcre (provided by the ppa).

I'll work in a workaround.

[luispabon]

Builds are up, they're working for me. If any of you could please docker pull and check to confirm I'd be thankful.

[mihitha]

8.0 also working for me now.

[tannoiser]

I also can confirm 7.4 works. I'll think to keep in any case the dist-upgrade just in case.
beside the size of the container, are there any other contraindications?

[JorgeSivil]

Thanks for the quick response @luispabon.

This leads me to ask you if there's a way to lock the container tag to prevent these kind of issues, so we can manually control the update of PHP / dependencies, giving more security on build status on this side.

I went to https://hub.docker.com/r/phpdockerio/php74-fpm/tags and it only shows "latest"

[luispabon]

Indeed there's only latest and it is like so by design. Static tags wouldn't have helped on this issue anyhow, unless I'd also gone and installed into the base image all of the php extension packages for that version of php. And I totally don't want to do that as the images would balloon in size.