-
Notifications
You must be signed in to change notification settings - Fork 82
Is this the same as gcr.io/google-appengine/php? #545
Comments
Also seeing this break our builds. PHP version is now not being honoured. |
Files are not being copied either. Confirmed using SHA as @qu0cster should work. But we might need long term solution for this and to GCP team, how can you avoid breaking your customer's build is important too. |
Can confirm the same issue. Attempted using gcr.io/google-appengine/php72. While it will get the correct PHP version, files are not being copied correctly. This is easily noted by failures to read composer.json that should be uploaded, as well as changes made in php.ini that are not being made. |
Thanks. You can use the tag |
@frost-byte @donmccasland Any thoughts? |
Hi guys, I have the same issue with the PHP7.4 version. None of the versions on the container registry google-appengine/global/php (and others php*) are up to date with this git. Latest tag doesn't manage php8 too. |
This is a question. Is this the same as gcr.io/google-appengine/php? If so, for some odd reason the PHP installed is not respecting the PHP version in the
composer.json
. When I built with gcr.io/google-appengine/php:latest, I notice the PHP version is 7.1.33 and the composer.json is asking for 7.2.* and it breaks everything.When I built with the previous image gcr.io/google-appengine/php@sha256:a85abb8c3aa946c9db321f72d3c46a0bc9aae97445dc3d3949d468f789caa8aa, it installed the correct 7.2.* version
The text was updated successfully, but these errors were encountered: