the build process is slower due to the need to handle an additional image and container.if Composer breaks something, it doesn't propagate out of the container.My current thoughts on separating Composer are:
#Dockerfile composer apk#
I couldn't figure any real sense in doing it vs simply apk adding composer to the main container, running composer install on the main container, and then removing Composer from it during the build (note that this affects neither the image size nor layer count the Composer binary could've been either added to the single RUN layer of all the other apps of the PHP/FPM source image or just apk added later during the build, and all the immediate files are removed eventually). ) to get all the dependencies, and later copies them to actual PHP/FPM container (a so-called multistage build). In one of the projects I work for, the production environment is set up in a way that uses an image with Composer only (i.e. Note: this question is not strictly PHP-oriented, since both Docker and Composer can be easily used outside of the PHP ecosystem (although such cases would be rather rare IMO).
0 kommentar(er)
