Current CTO exploring entrepreneurship on the side; coach; mentor; instructor.
Dedicated to promoting digital literacy and ideological diversity in tech.
Greedings I am Dimitrios Desyllas aka pc_magas.
I am a php software engineer in e-table.
I am interested in privacy enhancing technologies, cryptography and reverse engineering.
Location
Acharnes, Greece
Education
MSc at Digital Systems Security at Univercity Of Peireus
Pronouns
Yo Wazz up bro!
Work
Volunteer Sysadmin at ELLAK of Cyprus - open for opportunities.
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
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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: