docker-library / docker-library/php
Remove phpize deps from permanent image
Open
Nobody has claimed this yet.
Request
- Dominant language
- Dockerfile
- Stars
- 4k
- Forks
- 2k
- Avg merge
- 5d 21h
- Merged PRs (30d)
- 1
Description
Just wondering why we require perl in image php:7.1-fpm-stretch?
/usr/lib/x86_64-linux-gnu/perl => 19MB
# dpkg -S /usr/lib/x86_64-linux-gnu/perl
libperl5.24:amd64, perl-base: /usr/lib/x86_64-linux-gnu/perl
# apt-cache rdepends --installed perl
perl
Reverse Depends:
autoconf
adduser
perl-base
libdpkg-perl
debconf
libperl5.24
perl-modules-5.24
perl-base
perl-base
perl-modules-5.24
It appears to be related to phpize. Is there a need for it to be permanent in the image or could this be moved to a docker-php- script?
It's not relevant in production environments imo.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the php:7.1-fpm-stretch image's installed dependency chain, focusing on phpize and the docker-php- scripts mentioned in the issue. Determine whether Perl is needed at runtime or only during extension builds, then verify that the production image no longer includes the dependency while phpize workflows still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100