loading...
markdown guide
 

The more commands you run, the bigger your image will be.

However, an empty PHP image should be nowhere near 1GB in size.

Our complete application build for PHP is only 700 MB, and we haven't even started optimizing yet.

How are you reviewing your image sizes?

 

I am using a CI/CD pipeline (travis) and I try to use a single step for making the images. I build a multi-version (both debian-based and alpine-based) docker images for moodle (github.com/ellakcy/docker-moodle ) and I try to use a single RUN step for them.

So I thought whether replacing the header files after built with normal packages I can shave off few Megabytes of the final image as a complementary measure on the existing one: Reducing the amount of steps.

Also I see the sizes by typing into the terminal:

docker images
Classic DEV Post from May 19 '19

Solving Puzzles With High-Performance JavaScript

Premature optimization is the root of all evil. It's also the root of this article. I like programmi...

Dimitrios Desyllas profile image
Greedings I am Dimitrios Desyllas aka pc_magas. I am a php software engineer in e-table. I am interested in electron, C++, privacy enhancing terchnologies and cryptography

Sore eyes?

dev.to now has dark mode.

Go to the "misc" section of your settings and select night theme ❤️