Extend the Docker configuration

You can use the built-in extension mechanism of Docker to specify multiple compose files. The following example replaces the default value of the ENABLE_SENDMAIL environment variable.

1. Create a docker-compose-dev.yml file inside your project root directory and add the following content:

   1
   2
   3
   4
   5
   version: '2'
   services:
     deploy:
       environment:
         - ENABLE_SENDMAIL=false
   

2. Pass both configuration files while executing your commands. For example:

   1
   docker-compose -f docker-compose.yml -f docker-compose-dev.yml run deploy bash
   

Specify Docker build sources

To test changes to images or make more extensive changes to the containers, you must build them from source. You can do this by adding the build:context configuration to the docker-compose.override.yml file.

The following example defines the build context for the Web container. You can use the same technique to build from any of the images in the vendor/magento/magento-cloud-docker directory or any other Docker image, including local images that are resourced outside the project.

1
2
3
4
5
version: '2.1'
services:
  web:
    build:
      context: ./vendor/magento/magento-cloud-docker/images/nginx/1.9/

To update the container configuration and test iteratively, use the --force-recreate option to refresh the container build:

1
docker-compose up -d --force-recreate --build

Add a new version of existing service

In the magento/magento-cloud-docker package, the available service versions are determined by the Docker service images configured in the images directory. You add a new service version by creating a directory for the version and adding a Dockerfile and other files to configure the new version.

To add a new service version using a Dockerfile:

1. Clone the magento/magento-cloud-docker project to your local environment if necessary.

2. On the command line, change to the directory that contains the existing service version configurations.

   1
   cd magento-cloud-docker/images/<service-name>
   

3. Create a directory for the new version.

4. Change to the new directory.

5. Create a Dockerfile with any additional configuration details for the new version, such as supported plugins. You can use the Dockerfile from the previous version as a template.

6. Add the docker-entrypoint.sh and healthcheck files if needed.

7. Add any necessary .conf and .ini files for the service to the etc directory.

8. Build the image.

   1
   docker build -t test/<service-name>:<service-version>
   

9. After the build succeeds, test the changes by specifying the Docker build sources.

Add a new PHP extension

You can add PHP extensions to the PHP container by adding the extension configuration to the ExtensionResolver.php configuration file for Magento Cloud Docker.

To add a new PHP extension:

1. Clone the magento/magento-cloud-docker project to your local environment.

2. On the command line, navigate to the PHP directory.

   1
   cd magento-cloud-docker/src/Compose/Php
   

3. Add one or more extensions to the ExtensionResolver.php file:

   • Open the ExtensionResolver.php file for editing.

   • Specify the required extension in the getConfig method by specifying the extension type and dependency.

     For example, the following block adds the bcmath extension:

     1
     2
     3
     4
     5
     6
     7
     public static function getConfig(): array
     ...
     
     'bcmath' => [
         '>=7.0' => [self::EXTENSION_TYPE => self::EXTENSION_TYPE_CORE],
      ],
      ...
     

     In this case, the bcmath PHP core extension installs from docker-php-source images.

     The configuration you specify depends on the location of the extension source files and method of installation. You can add PHP core extensions from the official Docker PHP images, from the PECL repository, or using an installation script. For details on the configuration attributes and format for the getConfig method, see PHP extension configuration reference.

4. Enable the extension by default, or by adding it to the .magento.app.yaml file:

   • To enable an extension by default, add it to the DEFAULT_PHP_EXTENSIONS array in the ExtensionResolver.php file.

     1
     2
     3
     4
     5
     6
     7
     8
     9
     10
     11
     12
     13
     14
     15
     16
     17
     18
     19
     20
     21
     22
     23
     /**
      * Extensions which should be installed by default
      */
     public const DEFAULT_PHP_EXTENSIONS = [
         'bcmath',
         'bz2',
         'calendar',
         'exif',
         'gd',
         'gettext',
         'intl',
         'mysqli',
         'pcntl',
         'pdo_mysql',
         'soap',
         'sockets',
         'sysvmsg',
         'sysvsem',
         'sysvshm',
         'opcache',
         'zip',
     ];
     

   • If you add the extension to the .magento.app.yaml for your Cloud project, you must regenerate the Docker compose configuration file and restart the Docker container.

5. Add any required .ini files to the PHP FPM container configuration.

   • On the command line, navigate to the FPM image directory magento-cloud-docker/images/php/fpm:

     1
     cd ../../../images/php/fpm
     

   • Add each required .ini file to the etc directory.

   • For each .ini file that you add, you must add the following line to the Dockerfile (magento-cloud-docker/images/php/fpm/Dockerfile):

     1
     COPY etc/<filename>.ini /usr/local/etc/php/conf.d/<filename>.ini
     

6. Add any required .ini files to the PHP CLI container configuration.

   • On the command line, navigate to the CLI image directory magento-cloud-docker/images/php/cli.

     1
     cd ../cli
     

   • Add each required .ini file to the etc directory.

   • For each .ini file that you add, you must add the following line to the Dockerfile (magento-cloud-docker/images/php/cli/Dockerfile):

     1
     ADD etc/<file-name>.ini /usr/local/etc/php/conf.d/<filename>.ini
     

7. Generate an updated Dockerfile for all PHP image versions included in the package.

   1
   bin/ece-docker image:generate:php
   

8. Test the extension by specifying the Docker build sources.

PHP extension configuration reference

Use the following attributes to specify the PHP extension configuration in the getConfig method located in the ExtensionResolver.php file. The configuration you specify depends on method of installation: from the official Docker PHP images, from the PECL repository, or using an installation script.

For more information about extension types and extension installation, see How to install more PHP extensions section of the PHP, Docker Official Images page in Docker Hub.

Example: Core extension configuration

The following example shows the configuration for adding the PHP core extension gd in the ExtensionResolver.php file.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
public static function getConfig(): array
...
            'gd' => [
                '>=7.0 <=7.3' => [
                    self::EXTENSION_TYPE => self::EXTENSION_TYPE_CORE,
                    self::EXTENSION_OS_DEPENDENCIES => ['libjpeg62-turbo-dev', 'libpng-dev', 'libfreetype6-dev'],
                    self::EXTENSION_CONFIGURE_OPTIONS => [
                        '--with-freetype-dir=/usr/include/',
                        '--with-jpeg-dir=/usr/include/'
                    ],
                ],
                '>=7.4' => [
                    self::EXTENSION_TYPE => self::EXTENSION_TYPE_CORE,
                    self::EXTENSION_OS_DEPENDENCIES => ['libjpeg62-turbo-dev', 'libpng-dev', 'libfreetype6-dev'],
                    self::EXTENSION_CONFIGURE_OPTIONS => [
                        '--with-freetype=/usr/include/',
                        '--with-jpeg=/usr/include/'
                    ],
                ],

            ],
...

Example: PECL extension configuration

The following example shows the configuration for adding the gnupg extension from the PECL repository.

1
2
3
4
5
6
7
8
9
public static function getConfig(): array
...
            'gnupg' => [
                '>=7.0' => [
                    self::EXTENSION_TYPE => self::EXTENSION_TYPE_PECL,
                    self::EXTENSION_OS_DEPENDENCIES => ['libgpgme11-dev'],
                ],
            ],
...

Example: Configuration for extension installed using a script

The following example shows the configuration for installing the ioncube extension using an installation script.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
public static function getConfig(): array
...

            'ioncube' => [
                '>=7.0 <=7.3' => [
                    self::EXTENSION_TYPE => self::EXTENSION_TYPE_INSTALLATION_SCRIPT,
                    self::EXTENSION_INSTALLATION_SCRIPT => <<< BASH
cd /tmp
curl -O https://downloads.ioncube.com/loader_downloads/ioncube_loaders_lin_x86-64.tar.gz
tar zxvf ioncube_loaders_lin_x86-64.tar.gz
export PHP_VERSION=$(php -r "echo PHP_MAJOR_VERSION.'.'.PHP_MINOR_VERSION;")
export PHP_EXT_DIR=$(php-config --extension-dir)
cp "./ioncube/ioncube_loader_lin_\${PHP_VERSION}.so" "\${PHP_EXT_DIR}/ioncube.so"
rm -rf ./ioncube
rm ioncube_loaders_lin_x86-64.tar.gz
BASH
                ],
            ],
...