Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

alpine image rather outdated - makes it harder than it should be to install extensions #456

Closed
bernhardberger opened this issue Jun 23, 2017 · 4 comments

Comments

@bernhardberger
Copy link

Is there a way you might update the base image for the alpine builds? Especially for php 7.x as it is a massive pain to install various extensions or packages like GraphicsMagick..

Right now even the OpenSSL extension for PHP is broken on the 7.1 alpine image and basically impossible to install afterwards..

@yosifkit
Copy link
Member

Duplicate of #408. See also #448 and related issue docker-library/ruby#125 (comment).

In summary we are going to move to alpine 3.6 for php 7.2; it might make sense to have alpine 3.6 (and Debian Stretch) variants for 7.1 or 7.0 (though there already is way too many variants of the php image).

@sTywin
Copy link

sTywin commented Jul 10, 2017

In that case, I think the variant architecture needs a bit of re-think. IMO it is not reasonable to peg a specific rootfs container revision for extended periods of time. In other threads, you have mentioned wanting to stay as close to upstream as possible [1] -- I agree with this, except that I would consider the base Alpine image to be included in the definition of upstream. The output is, after all, a combination of the two.

I admit that this complicates versioning. However, if the build process is entirely automated anyway, it shouldn't be too hard to have something like php:7-alpine point to alpine:latest, and php:7-alpine-3.4 point to alpine:3.4, and so on. If the scheme is well-defined, it's easy for people to pull whatever specific image they want.

Edit:

  1. Upon re-reading my reply, I realize you probably meant from a code divergence standpoint as opposed to a time standpoint. My comment remains, though -- there is value in keeping base images up to date (security fixes, tools people expect to be available, etc).

@yosifkit
Copy link
Member

@sTywin, I agree that making the default distribution more obvious is a good thing (like php:7.1-apache-jessie or php:7.1-alpine3.4). I've started over in golang (docker-library/golang#170) since it was much simpler. Once that one is done, @tianon and I can spread it to other images we control (like php). Then we can look to add more variations for stretch and alpine3.6 in php (and our other images). 😄

@yosifkit
Copy link
Member

yosifkit commented Oct 3, 2017

Closing in favor of discussion to create base distro update process #504.

@yosifkit yosifkit closed this as completed Oct 3, 2017
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

No branches or pull requests

3 participants