Images are kinda huge, aren't they?

[silentvick]

Maybe it's not a big deal, but still. ~800Mb for apache-php? Well, that's a lot in comparison with other images that weights ~250 Mb in average. I guess it's because of build tools that are used to compile php from source. Anyway, I wonder if anything can be done with it?

[tianon]

I wonder if buildpack-deps even makes sense to use here, since we don't really have a way to create an "onbuild" PHP image. Swapping that out for just debian would slim us down a huge amount.

cc @yosifkit

[yosifkit]

Oh, good idea. 👍

[tianon]

I'm build-testing a few things on this now. I think we'll want to make sure we have the deps required to phpize in the resulting image, but other than that we should stay as slim as we can, IMO.

[thaJeztah]

Thanks @tianon that's quite an improvement.

Still, ~400mb compared to a standard debian + apache + php (with a lot more extension) of ~240mb is quite a difference.

Any idea what makes this difference?