Adding support for php/pie to install php extensions #564
Replies: 2 comments 1 reply
-
In the meantime, if you wish to use pie, you can add this to your docker image
Then use Note: You may need to install additional tools such as |
Beta Was this translation helpful? Give feedback.
-
I really was hoping that I could come up with a solution to have this in v4.0, because I am excited to see a modern replacement for PECL. The problem with PIE (as of today)It seems like PIE might add some bloat to the images? That's what I really liked about More discussion@nicosalvadore pointed me to this conversation, which I also chimed in on: Right now I am hesitant to implement PIE because it doesn't seem to have a "container first" design like I need to learn more and then I will definitely pursue a solution on this 💯 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
👉 Describe the problem
Today, the docker images are using mlocati/docker-php-extension-installer to install php extensions. Which pulls the extensions from PECL.
According to PECL website, PECL is being deprecated. A new tool called PIE is the official new way to install extensions.
👥 Problem evidence & reach
Everyone using PECL is or will be impacted sooner or later.

https://pecl.php.net/
🏆 How to solve this problem
According to the PIE docs, PIE is distributed as a PHAR, just like Composer. I would then suggest to include this package in the base docker images to allow and document the new way to install php extensions.
The current package mlocati/docker-php-extension-installer should still be in the docker images, to ensure backwards compatibility.
🥰 Describe the "impact" on users?
User would be presented with two ways to install php extensions : one legacy, and one officially supported.
Thanks in advance :)
Beta Was this translation helpful? Give feedback.
All reactions