Skip to content

fix(Containers): build PECL extensions from GitHub release sources - #8804

Draft
szaimen wants to merge 1 commit into
mainfrom
fix/pecl-to-docker-php-ext-install
Draft

szaimen wants to merge 1 commit into
mainfrom
fix/pecl-to-docker-php-ext-install

Conversation

@szaimen

@szaimen szaimen commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator

pecl.php.net is not reliably reachable from GitHub runners, which makes pecl install fail with "No releases available for package". Download the release tarballs from GitHub instead and build them with docker-php-ext-install. Versions are now defined as ARGs which the update workflows bump. smbclient is pinned to its latest stable release.

Summary

  • The PR was tested and verified that it works locally
  • Or will be tested after merge on a dedicated test instance (available for maintainers)
  • Sign-off message is added to all commits
  • Tests (playwright if possible) are included
  • Screenshots before/after for front-end changes
  • Documentation has been updated or is not required
  • Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
  • Milestone next added

AI (if applicable)

  • The content of this PR was partly or fully generated using AI

pecl.php.net is not reliably reachable from GitHub runners, which makes
pecl install fail with "No releases available for package". Download the
release tarballs from GitHub instead and build them with
docker-php-ext-install. Versions are now defined as ARGs which the update
workflows bump. smbclient is pinned to its latest stable release.

Assisted-by: ClaudeCode:claude-opus-5-5
Signed-off-by: Simon L. <szaimen@e.mail.de>
@szaimen szaimen added 2. developing Work in progress enhancement New feature or request labels Oct 8, 2026
@szaimen

szaimen commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator Author

@pabzm WDYT about something like this? We could get rid of the PECL dependency then...

@pabzm

pabzm commented Oct 14, 2026

Copy link
Copy Markdown
Member

I welcome to get rid of PECL, since it's deprecated as a whole already. But I would prefer to replace it by it successor PIE instead of installing manually, because it keeps our scripts shorter and cleaner and avoids some complexities that (often) arise from installing packages from source.

At least where possible: lib-smbclient appears not to be available through PIE, yet. pecl-mail-imap` can be replaced by https://root.packagist.org/packages/sirlouen/imap. The others are all available, as far as I can tell.

What do you think about that?

@szaimen

szaimen commented Oct 14, 2026 •

Copy link
Copy Markdown
Collaborator Author

What do you think about that?

I inviestigated this possibility already with Claude Opus 5.5 but it looked like we would need to work around some problems there and as you said not all extensions are available there yet so we would need to migrate to a hybrid approach. Due to that I figured it might be better to completely migrate off this external infrastructure...

@pabzm

pabzm commented Oct 14, 2026

Copy link
Copy Markdown
Member

Ok, I don't care that much. But then please refactor the code, e.g. by using a function, so it gets less repetitive.

This branch has not been deployed

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

Labels

2. developing Work in progress enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants