Composer-docker VS lamp-docker

The same principle applies to any other images you may depend on, such as composer for dependency installation. Select the image tag that matches the major composer version you're using on your machine — composer:2 instead of composer:latest.

I've got a local version of PHP installed, but I really don't need it. Composer has an official docker container: https://hub.docker.com/_/composer/

I found on the docs of the composer image, in the Troubleshooting section, that composer should not be used that way. So I put it inside the Php image with COPY --from=composer /usr/bin/composer /usr/bin/composer and it worked. Thanks for the help u/effata!

I run most of the projects I develop on through a docker image. If it's a PHP project with composer dependencies, I use a composer image to install its dependencies, when I want to run it I use a php image. If the PHP image does not include the dependencies required for the project, I will look for an image within the project that is used, or build my own image serving the purpose. I like to make things easy to run and use, so that if I leave a project for a while I want it to be easy to get started again. If the project requires multiple things running, like a database, I setup docker-compose to make it easy to start a PHP container and database container alongside eachother that can communicate.

There is a hard coded case for this now in the project https://github.com/composer/docker/blob/master/1.10/docker-entrypoint.sh#L6

The /app directory is specified working directory, from composer image via https://github.com/composer/docker/blob/582c6f4e10b6b8fbf9bc1c5b02d6ec24694fe8d4/2.0/Dockerfile#L60.

I use a LAMP docker environment: https://github.com/danielefavi/lamp-docker