Skip to content

Replace PECL with PIE#998

Open
furai wants to merge 1 commit intodocker-library:masterfrom
furai:feature/pie
Open

Replace PECL with PIE#998
furai wants to merge 1 commit intodocker-library:masterfrom
furai:feature/pie

Conversation

@furai
Copy link

@furai furai commented Feb 18, 2026

This PR aims to replace PECL with PIE. I've opted for using bind mount for pie to not bloat the image with pie executable.

If we'd like to keep pie in the image then we can replace the bind mount with:

COPY --from=ghcr.io/php/pie:bin /pie /usr/local/bin/pie

The executable is around 12 MB.

Other caveats are that PHP base image is compiled with pear support so the PECL itself is still there.

Let me know if this PR is acceptable or you require any changes.

@tianon
Copy link
Member

tianon commented Feb 18, 2026

https://github.com/docker-library/official-images#repeatability

No official images can be derived from, or depend on, non-official images

(meaning ghcr.io/php/pie:bin is not an acceptable dependency here because it is not part of the upstream program)

See also docker-library/php#1554 for a relevant discussion.

Can you perhaps explain why this might be relevant to the WordPress image? Does the end result of the build actually change in any meaningful way?

@furai
Copy link
Author

furai commented Feb 18, 2026

Oh I didn't know it's against policy. So what it means is that until php upstream switches from pecl (as it's deprecated now) to pie there won't be any way to get pie into official wp image?

If I knew it wasn't desired I wouldn't have created this PR. I just heard that pecl is deprecated and in my custom images I've switched to pie and I thought maybe it's good idea to contribute it to upstream.

One other reason was that in past pecl had problems with installing imagick.

Feel free to close this PR if you think it's incorrect approach.

Thank you for your time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments