Docker compose php composer install

Install composer in custom Docker image

Before Docker 17.05 dropped mid-2017, installing software inside a custom Docker image followed the same process as installing it on the host. For example, you can install composer to /usr/local/bin on a desktop by running the following curl command as root.

curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer 

# Dockerfile FROM php:7.4.1-fpm # Install Composer RUN curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer 

Watch

Ta-da! It works, but it relies on curl and an internet connection. Docker 17.05 brought a cleaner, less curl-y, internet-y way.

Multi-stage builds and COPY

Simply replace the RUN instruction with the COPY instruction seen below. You can see that we are copying from the composer image from /usr/bin/composer to /usr/bin/composer in the new image. Now let’s see it in action, (as documented at https://hub.docker.com/_/composer):

# Dockerfile FROM php:7.4.1-fpm # Install Composer COPY --from=composer /usr/bin/composer /usr/bin/composer 

Watch

Top comments (10)

I have followed the above guides. It stops once composer is installed — and I can confirm it is running in my own container.

How do I now deploy packages within that container?

In my case, I require 2 packages:

My issue is that I would like to map an existing directory that contains my existing PHP pages & scripts in to /var/www/html . If I try this, the composer packages are not installed — I expect because they are overwritten with the mapping?

If I omit the directory mapping, I can see the relevant composer files in the root folder (/var/www/html). But now I have no PHP content.

1 like Like Comment button

Источник

Introduction#

Composer is a tool for dependency management in PHP. It allows you to declare the libraries your project depends on and it will manage (install/update) them for you.

Dependency management#

Composer is not a package manager in the same sense as Yum or Apt are. Yes, it deals with «packages» or libraries, but it manages them on a per-project basis, installing them in a directory (e.g. vendor ) inside your project. By default, it does not install anything globally. Thus, it is a dependency manager. It does however support a «global» project for convenience via the global command.

This idea is not new and Composer is strongly inspired by node’s npm and ruby’s bundler.

1. You have a project that depends on a number of libraries.
2. Some of those libraries depend on other libraries.

1. Enables you to declare the libraries you depend on.
2. Finds out which versions of which packages can and need to be installed, and installs them (meaning it downloads them into your project).
3. You can update all your dependencies in one command.

See the Basic usage chapter for more details on declaring dependencies.

System Requirements#

Composer in its latest version requires PHP 7.2.5 to run. A long-term-support version (2.2.x) still offers support for PHP 5.3.2+ in case you are stuck with a legacy PHP version. A few sensitive php settings and compile flags are also required, but when using the installer you will be warned about any incompatibilities.

Composer needs several supporting applications to work effectively, making the process of handling package dependencies more efficient. For decompressing files, Composer relies on tools like 7z (or 7zz ), gzip , tar , unrar , unzip and xz . As for version control systems, Composer integrates seamlessly with Fossil, Git, Mercurial, Perforce and Subversion, thereby ensuring the application’s smooth operation and management of library repositories. Before using Composer, ensure that these dependencies are correctly installed on your system.

Composer is multi-platform and we strive to make it run equally well on Windows, Linux and macOS.

Installation — Linux / Unix / macOS#

Downloading the Composer Executable#

Composer offers a convenient installer that you can execute directly from the command line. Feel free to download this file or review it on GitHub if you wish to know more about the inner workings of the installer. The source is plain PHP.

There are, in short, two ways to install Composer. Locally as part of your project, or globally as a system wide executable.

Locally#

To install Composer locally, run the installer in your project directory. See the Download page for instructions.

The installer will check a few PHP settings and then download composer.phar to your working directory. This file is the Composer binary. It is a PHAR (PHP archive), which is an archive format for PHP which can be run on the command line, amongst other things.

Now run php composer.phar in order to run Composer.

You can install Composer to a specific directory by using the —install-dir option and additionally (re)name it as well using the —filename option. When running the installer when following the Download page instructions add the following parameters:

php composer-setup.php --install-dir=bin --filename=composer

Now run php bin/composer in order to run Composer.

Globally#

You can place the Composer PHAR anywhere you wish. If you put it in a directory that is part of your PATH , you can access it globally. On Unix systems you can even make it executable and invoke it without directly using the php interpreter.

After running the installer following the Download page instructions you can run this to move composer.phar to a directory that is in your path:

mv composer.phar /usr/local/bin/composer

If you like to install it only for your user and avoid requiring root permissions, you can use ~/.local/bin instead which is available by default on some Linux distributions.

Note: If the above fails due to permissions, you may need to run it again with sudo .

Note: On some versions of macOS the /usr directory does not exist by default. If you receive the error «/usr/local/bin/composer: No such file or directory» then you must create the directory manually before proceeding: mkdir -p /usr/local/bin .

Note: For information on changing your PATH, please read the Wikipedia article and/or use your search engine of choice.

Now run composer in order to run Composer instead of php composer.phar .

Installation — Windows#

Using the Installer#

This is the easiest way to get Composer set up on your machine.

Download and run Composer-Setup.exe. It will install the latest Composer version and set up your PATH so that you can call composer from any directory in your command line.

Note: Close your current terminal. Test usage with a new terminal: This is important since the PATH only gets loaded when the terminal starts.

Manual Installation#

Change to a directory on your PATH and run the installer following the Download page instructions to download composer.phar .

Create a new composer.bat file alongside composer.phar :

C:\bin> echo @php "%~dp0composer.phar" %*>composer.bat

PS C:\bin> Set-Content composer.bat '@php "%~dp0composer.phar" %*'

Add the directory to your PATH environment variable if it isn’t already. For information on changing your PATH variable, please see this article and/or use your search engine of choice.

Close your current terminal. Test usage with a new terminal:

Composer version 2.4.0 2022-08-16 16:10:48

Docker Image#

Composer is published as Docker container in a few places, see the list in the composer/docker README.

docker pull composer/composer docker run --rm -it -v "$(pwd):/app" composer/composer install

To add Composer to an existing Dockerfile you can simply copy binary file from pre-built, low-size images:

# Latest release COPY --from=composer/composer:latest-bin /composer /usr/bin/composer # Specific release COPY --from=composer/composer:2-bin /composer /usr/bin/composer

Read the image description for further usage information.

Note: Docker specific issues should be filed on the composer/docker repository.

Note: You may also use composer instead of composer/composer as image name above. It is shorter and is a Docker official image but is not published directly by us and thus usually receives new releases with a delay of a few days. Important: short-aliased images don’t have binary-only equivalents, so for COPY —from approach it’s better to use composer/composer ones.

Using Composer#

Now that you’ve installed Composer, you are ready to use it! Head on over to the next chapter for a short demonstration.

Found a typo? Something is wrong in this documentation? Fork and edit it!

Composer and all content on this site are released under the MIT license.

Источник

PHP Composer with Docker development

Composer is a de-facto standard for managing PHP packages. Good practice however is to not include it in the production Docker images.

Let’s first take a look at how to use Composer with Docker in general. There are some established best practices:

1. Official Docker Composer image

• Official Composer Docker image
• Simple to use
• Separation of development and production

• When your application requires additional PHP extensions, or is using the scripts defined in the composer.json file, you’ll either need to install them in this additional Composer image or pass the —ignore-platform-reqs and —no-scripts options and run scripts separately.

docker run -it --rm -v `pwd`:/app composer install 

2. Custom installation

You can also simply install Composer per project basis on your own in your Dockerfile :

RUN php -r "readfile('http://getcomposer.org/installer');" | php -- --install-dir=/usr/bin/ --filename=composer 

If you’ll need to install PHP packages from sources instead of zip archives you will also need to install version control system such as Git.

Composer installation in general requires several PHP extensions installed:

and few system packages, depending on what version system you will use:

RUN apt-get update && apt-get -y --no-install-recommends install git \ && php -r "readfile('http://getcomposer.org/installer');" | php -- --install-dir=/usr/bin/ --filename=composer \ && rm -rf /var/lib/apt/lists/* 

Composer can be then used in the following ways:

docker run -it --rm -v `pwd`:/usr/src/myapp -w /usr/src/myapp php-app composer 

docker-compose run --rm -w /var/www/app app composer 

Advantage of custom installation per project is that Composer is running with the same PHP installation as your application and can pass the PHP extensions checkings.

• Composer is present also in production and to have separate production image you’ll need to create more than one Dockerfile for application or use Docker build arguments

Docker build arguments

When building production images, you can avoid adding Composer in your image with build arguments. The following example uses Docker build arguments:

FROM php:7.2 ARG APP_ENV=prod RUN if [ $APP_ENV> = "dev" ]; then \ php -r "readfile('http://getcomposer.org/installer');" | php -- --install-dir=/usr/bin/ --filename=composer; \ fi 

You can set the build arguments in the Docker Compose files and manage how the image is build for each of your environment:

# docker-compose.dev.yaml version: '3.4' services: app: volumes: - ../:/var/www/app build: args: - APP_ENV=dev ports: - 80:80 

PHP.earth Docker images

PHP.earth Docker images come with optional Composer package which also includes all required PHP extensions dependencies.

For Alpine Linux there is a composer package available:

FROM phpearth/php:7.2-nginx RUN apk add --no-cache composer 

Prestissimo Composer plugin

Prestissimo is a Composer plugin for faster parallel downloading of PHP packages.

FROM phpearth/php:7.2-nginx ARG APP_ENV=prod RUN if [ $APP_ENV> = "dev" ]; then \ apk add --no-cache git openssh composer \ && composer global require hirak/prestissimo; \ fi 

Источник