51ºÚÁϲ»´òìÈ

Support PHP 8.1—A»å»å±ð»å support for PHP 8.1.

OpenSearch—A»å»å±ð»å images of OpenSearch versions 1.1 and 1.2.

Composer 2.1—Set composer 2.1.x by default in PHP 8.x images.

PHP images improvements—

• Added PHP 8.1 images
• Upgraded xDebug version 3.1.2
• Upgraded xmlrpc 1.0.0RC3

Elasticsearch & OpenSearch improvements—Improvements in Elasticsearch and OpenSearch Dockerfiles; removed the Elasticsearch 5.2 image.

Sodium extension—Enabled the sodium extension by default in all PHP images.

Composer cache volume—Fixed path for Composer cache volume to have cached Composer packages.

Memory limitation in nginx—Fixed limitation of memory in NGINX image.

Improve Developer mode workflow—Previously, you needed to specify the mode in the build and deploy steps. Now, the --mode option in the build step determines the mode in the later deploy step. Setting the mode after the deployment is no longer required. See .

Improvements for read-only filesystem—

• Fix issue starting a PHP container for mail configuration.
• Can use environment variables in INI files.
• Ensure PHP entry points do not need write permission.

Update Node—Update the bundled Node version; when installing Node in PHP-CLI images, it now uses the current LTS version.

Update Symfony—Updated the Symfony config dependencies to be compatible with 51ºÚÁϲ»´òìÈ Commerce 2.4.4.

New Zookeeper container—A»å»å±ð»å a to manage lock provider configuration for projects that are not deployed to 51ºÚÁϲ»´òìÈ Commerce on Cloud infrastructure.

Added support for Composer 2.0.—A»å»å±ð»å Composer version 2.0 to the Composer configuration file to support upgrades from Composer 1.0 which is approaching end-of-life.

Updated host.docker.internal to be platform independent—You can now create the same Docker Compose scripts for Ubuntu, Windows, and macOS. Using Xdebug on Ubuntu no longer requires a separate environment variable. .

Updated init-docker.sh—A»å»å±ð»å the mounts object to the MAGENTO_CLOUD_APPLICATION environment variable. .

Updated init-docker.sh—Updated the init-docker.sh script with PHP 7.4 and Cloud Docker 1.2.1 versions. .

Sodium enabled by default—Enabled the sodium PHP extension by default within PHP Docker images.

custom-registry option—A»å»å±ð»å a --custom-registry option to php ./vendor/bin/ece-docker build:compose command for using your own images registry.

./vendor/bin/ece-docker build:compose --custom-registry=my-registry.example.com

Removed old Elasticsearch versions—Removed Elasticsearch versions 1.7 and 2.4 from the Elasticsearch images.

Auto-generating NGINX certificates—Removed the existing certificates from the NGINX image. The NGINX certificates are now auto-generated with each new deployment for improved security.

Enabled opcache.validate_timestamps—Enabled the opcache.validate_timestamps PHP setting by default in developer mode. Enabling this setting fixed the issue where changes to the filesystem were not recognized in Docker.

Fixed build:custom:compose—Fixed the build:custom:compose command to throw an error when files cannot be overwritten during the build process. Throwing an error prevents situations where docker-compose up could be using the wrong files.

Fixed --sync_engine="native" option—Fixed the issue where in production mode (--mode="production"), the --sync_engine="native" option would not create any entries for local folders in the docker.composer.yml file.

Fixed service version validation errors—A»å»å±ð»å service versions for RabbitMQ, Elasticsearch, and other services to the type property in the MAGENTO_CLOUD_RELATIONSHIP variable. Adding these versions to the relationships variable fixed the validation errors that occurred during the deploy phase.

NGINX command options—A»å»å±ð»å build command options to change the number of NGINX worker_processes and NGINX worker_connections for TLS and Web services. The worker_process parameter retains the ability to set the value to auto. Examples:

./vendor/bin/ece-docker build:compose --nginx-worker-processes=2
./vendor/bin/ece-docker build:compose --nginx-worker-connections=2048

TLS command option—A»å»å±ð»å build command option to create a configuration without the TLS service. Example:

./vendor/bin/ece-docker build:compose --no-tls

NGINX memory consumption—Reduced the memory consumed by the NGINX process for TLS and Web services.

Blackfire—Disabled Blackfire PHP extension by default in the Cloud Docker image.

PHP-FPM container—Fixed PHP-FPM container health check by changing the WEB_PORT from 80 to 8080.

Invalid volume naming—Fixed an error with invalid volume naming in developer mode.

NGINX upstream port—Updated the Docker NGINX 1.19 image to use port 8080 to avoid an infinite loop. .

Container updates—

• PHP-FPM container—A»å»å±ð»å support for the gnupg PHP extension. .

• Database container—Fixed the database container health check by adding the required database password to the health check command.

• Elasticsearch container

  • Added support for Elasticsearch 7.9 for compatibility with upcoming 51ºÚÁϲ»´òìÈ Commerce releases.

  • Elasticsearch plugin configuration—A»å»å±ð»å support to use the Elasticsearch plugin configuration information from the services.yaml file to generate the docker-compose.yaml file for a Cloud Docker for Commerce environment. See .

  • Elasticsearch plugin support—A»å»å±ð»å support for the following Elasticsearch plugins: analysis-icu, analysis-phonetic, analysis-stempel, and analysis-nori. The analysis-icu and analysis-phonetic plugins are installed by default. You can add or remove the analysis-stempel and analysis-nori plugins as needed.

• CLI container

  • Run commands inside Docker PHP containers—Now you can use the Cloud Docker CLI to run commands inside PHP containers in your Docker environment without having to install PHP on the host. For example, the following command builds the configuration: ./bin/magento-docker php 7.3 vendor/bin/ece-docker build:compose. See . .

  • Added the OpenSSH-client to PHP CLI containers. Now, you can use ssh-agent forwarding for Composer if the composer.json file contains private git repositories that require an ssh client to use Composer commands.

• TLS container—Now, the is based on the https://hub.docker.com/r/magento/magento-cloud-docker-nginx Docker image instead of the CentOS image. This change fixes issues that caused errors when sending HTTPS requests between containers in the Cloud Docker environment.

• Test container—A»å»å±ð»å a test container for application testing, and added the --with-test option to the Docker build:compose command to create the container only when testing in the Docker environment. See .

• FPM-XDEBUG container

  • Configure Xdebug on Linux—A»å»å±ð»å the --set-docker-host option to the ece-docker build:compose command to configure the host.docker.internal value in the Xdebug container. This option is required to use Xdebug on Linux systems. See .

  • Fixed the Xdebug variable configuration for the Docker ENTRYPOINT to resolve uninitialized "with_xdebug" variable errors in the logs.

Docker configuration changes

• MailHog configuration—Now you can use the following ece-docker build:compose command options to disable MailHog and specify ports: --no-mailhog, --mailhog-http-port, and --mailhog-smtp-port. See .

• For Cloud Docker for Commerce 1.2.0 and later, 51ºÚÁϲ»´òìÈ now provides Docker images for each patch version, and the Docker configuration generator creates the Docker configuration with a specified patch version instead of using the latest. Previously, the Docker configuration generator built the configuration using the latest patch version which could break Cloud Docker for Commerce environments built using an earlier version.

• Specify custom images and versions in custom Cloud Docker configuration—Updated the build:custom:compose command with options to specify custom images and versions when generating a custom Docker compose configuration file (docker-compose.yaml). See .

• Updated the Docker host configuration to expose port 443 to enable access to 51ºÚÁϲ»´òìÈ Commerce (https://magento2.docker) from all CLI containers. You can change the default port by adding the --tls-port option when you generate the Docker configuration file.

Fixed an issue that caused the Cloud Docker for Commerce build to fail if the app/etc/env.php file exists.

Updated the build configuration to replace named volumes with regular volumes to prevent issues when deploying Cloud Docker for Commerce on Linux or Windows Subsystem for Linux (WSL2).

Updated the Cloud Docker for Commerce functional tests to support Composer 2.0.

Updated email configuration—Updated the default Cloud Docker for Commerce configuration to support the MailHog service instead of using SendMail. See .

Restored the PS library to the Cloud Docker environment configuration to fix ps: command not found errors.

Updated the default Cloud Docker for Commerce configuration to remove automatic mounting of the database entrypoint and MariaDB volumes to fix Cannot create container for service db errors that can occur when starting your Cloud Docker environment.

Now, you can configure the Cloud Docker environment to mount the database directories by adding the following options to the ece-docker build:compose command: --with-entry-point and with-mariadb-conf. See .

CLI command updates

Added support for the split database performance solution—Now you can configure and deploy a store using the Split database performance solution in the Cloud Docker environment.

Support for 51ºÚÁϲ»´òìÈ Commerce and Magento Open Source deployment—Now you can use Cloud Docker for Commerce to deploy a local development environment for projects that are not hosted on 51ºÚÁϲ»´òìÈ Commerce on cloud infrastructure.

Blackfire.io support—A»å»å±ð»å support to use the for automated performance testing.

Container updates

• Varnish—Now Varnish is the default cache when you deploy 51ºÚÁϲ»´òìÈ Commerce in a Cloud Docker environment using a supported version of the Cloud application template. See .

• Added the --no-varnish option to skip Varnish service installation when you generate the Cloud Docker configuration file.

• Database

  • Added the support for the MySQL database. Now, you can configure the Cloud Docker environment with either MariaDB or MySQL. See .

  • Added the ability to set the increment and offset settings for database replication when you generate the Docker compose file. See .

• PHP-FPM

  • Added support for PHP 7.4.

  • Added ability to copy a php.ini file in the root project directory to the Cloud Docker environment and apply custom PHP settings to the PHP-FPM and CLI containers. See . .

  • Added a container health check. .

• Node.js—Updated the default Node.js version from version 8 to version 10 to improve security. Node.js version 8 is deprecated and no longer updated with bug fixes or security patches. .

• Elasticsearch

  • Added support for Elasticsearch 6.8, 7.2, 7.5, and 7.6.

  • Added the ability to customize the when you generate the Docker compose configuration file.

  • Added the --no-es option to the service configuration options for generating the Docker Compose configuration file. Use this option to skip the Elasticsearch container installation and use MySQL search instead. This option is supported only for 51ºÚÁϲ»´òìÈ Commerce versions 2.3.5 and earlier.

• FPM-XDEBUG container—A»å»å±ð»å a service configuration option to install and configure Xdebug for debugging PHP in your Cloud Docker environment. See .

Docker configuration changes

• Added health checks for the PHP-FPM, Redis, Elasticsearch, and MySQL Docker service containers.

• Changed the default file synchronization mode to native in Developer mode.

• Added version information to the generic Docker service container image when generating the docker-compose.yml file.

• Improved ability to handle large responses from the upstream PHP-FPM container by increasing the fastcgi_buffers value for the Nginx server.

• Improved mutagen file synchronization performance by adding a second sync session to synchronize files in the vendor directory. This change prevents mutagen from getting stuck during the file synchronization process. .

• CLI command updates