Execute bin/magento and Composer within Docker containers

Link copied

Attach video time

We’re working from the Magento project root, where the src directory contains the Magento source code. In a Docker Magento project, run bin/magento from the project root rather than from the src directory.

The project-root bin/magento script acts as a proxy. It calls bin/cli and passes the bin/magento command and any additional arguments into the Docker container:

bin/magento

The $@ portion of the script forwards any remaining arguments to the command. As a result, the Magento command runs inside the container instead of on your host machine.

If you run bin/magento from the src directory, you may get an error because your host machine might not have the PHP dependencies required to execute Magento. Running it from the project root ensures that Docker provides the correct PHP environment and dependencies.

Use the same approach for Composer. Run bin/composer from the project root instead of the composer command:

bin/composer install
bin/composer update
bin/composer require vendor/package

The composer binary runs on your host machine, while bin/composer executes Composer inside the Docker container. This ensures that the project uses the Composer version and dependencies provided by the container rather than whatever happens to be installed locally.

Running Composer through bin/composer is especially important for commands such as install, update, and require, since differences in PHP versions, Composer versions, or installed extensions on your host machine can otherwise cause inconsistent results.