Cloud Docker package
- Topics:
- Cloud
- Docker
- Release Notes
CREATED FOR:
- Admin
- Developer
The magento/magento-cloud-docker
package provides functionality and Docker images to deploy Adobe Commerce to a local Cloud environment. These release notes describe the latest improvements to this package, which is a component of Cloud Tools Suite for Commerce.
The magento/magento-cloud-docker
package uses the following version sequence: <major>.<minor>.<patch>
The release notes include:
v1.4.1
Release date: February 6, 2025
v1.4.0
Release date: October 7, 2024
v1.3.7
Release date: April 8, 2024
v1.3.6
Release date: July 31, 2023
v1.3.5
Release date: March 10, 2023
v1.3.4
Release date: October 27, 2022
v1.3.3
Release date: September 13, 2022
-
-
-
init-docker.sh
script.
v1.3.2
Release date: March 31, 2022
v1.3.1
Release date: March 10, 2022
-
-
-
-
- Added PHP 8.1 images
- Upgraded xDebug version 3.1.2
- Upgraded xmlrpc 1.0.0RC3
-
-
sodium
extension by default in all PHP images. -
-
v1.3.0
Release date: October 25, 2021
-
--mode
option in thebuild
step determines the mode in the laterdeploy
step. Setting the mode after the deployment is no longer required. See Developer mode. -
- 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.
-
-
v1.2.4
Release date: July 29, 2021
-
Zookeeper
container—Added a Zookeeper container to manage lock provider configuration for projects that are not deployed to Adobe Commerce on Cloud infrastructure. -
v1.2.3
Release date: June 14, 2021
-
-
-
ioncube
extension for PHP 7.4 image—Theioncube
extension has been re-added to the PHP 7.4 image after having been initially excluded from the PHP 7.3 to PHP 7.4 upgrade. Submitted by mattskr. -
manual-native
—Themanual-native
file synchronization option provides manual control over synchronization, which provides the best performance for macOS and Windows environments. Read about using themanual-native
option in Developer mode and Synchronizing data in a Docker developer environment. -
up
anddown
commands—The--volume
option was removed from thebin/magento-docker up
andbin/magento-docker down
commands, replaced by the newbin/magento-docker init
command with a data loss warning. This change helps prevent the accidental data loss. Submitted by joeshelton-wagento. -
CN
value for the generated certificate—Removed the hardcodedCN
value from the Dockerfile. This value created a certificate error (NET::ERR_CERT_INVALID
) that caused the--host
option for theece-docker build:compose
command to be ignored.
v1.2.2
Release date: April 20, 2021
-
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. Fix submitted by Igor Vitol. -
mounts
object to theMAGENTO_CLOUD_APPLICATION
environment variable. Fix submitted by Chiranjeevi. -
init-docker.sh
script with PHP 7.4 and Cloud Docker 1.2.1 versions. Fix submitted by Adarsh Manickam. -
sodium
PHP extension by default within PHP Docker images. -
custom-registry
option—Added a--custom-registry
option tophp ./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
-
-
-
opcache.validate_timestamps
—Enabled theopcache.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. -
build:custom:compose
—Fixed thebuild:custom:compose
command to throw an error when files cannot be overwritten during the build process. Throwing an error prevents situations wheredocker-compose up
could be using the wrong files. -
--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 thedocker.composer.yml
file. -
type
property in theMAGENTO_CLOUD_RELATIONSHIP
variable. Adding these versions to therelationships
variable fixed the validation errors that occurred during the deploy phase.
v1.2.1
Release date: December 21, 2020
-
worker_processes
and NGINXworker_connections
for TLS and Web services. Theworker_process
parameter retains the ability to set the value toauto
. Examples:./vendor/bin/ece-docker build:compose --nginx-worker-processes=2 ./vendor/bin/ece-docker build:compose --nginx-worker-connections=2048
-
./vendor/bin/ece-docker build:compose --no-tls
-
-
-
WEB_PORT
from80
to8080
. -
-
v1.2.0
Release date: November 9, 2020
-
-
-
-
-
Added support for Elasticsearch 7.9 for compatibility with upcoming Adobe Commerce releases.
-
Elasticsearch plugin configuration—Added support to use the Elasticsearch plugin configuration information from the
services.yaml
file to generate thedocker-compose.yaml
file for a Cloud Docker for Commerce environment. See Elasticsearch plugins. -
Elasticsearch plugin support—Added support for the following Elasticsearch plugins:
analysis-icu
,analysis-phonetic
,analysis-stempel
, andanalysis-nori
. Theanalysis-icu
andanalysis-phonetic
plugins are installed by default. You can add or remove theanalysis-stempel
andanalysis-nori
plugins as needed.
-
-
-
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 Cloud Docker CLI. Fix submitted by G Arvind from Zilker Technology. -
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.
-
-
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. -
--with-test
option to the Dockerbuild:compose
command to create the container only when testing in the Docker environment. See application testing. -
-
--set-docker-host
option to theece-docker build:compose
command to configure thehost.docker.internal
value in the Xdebug container. This option is required to use Xdebug on Linux systems. See Configure Xdebug for Docker. -
uninitialized "with_xdebug" variable
errors in the logs. Fix submitted by Florent Olivaud
-
-
-
-
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 Set up email. -
For Cloud Docker for Commerce 1.2.0 and later, Adobe 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 Build a custom Docker Compose configuration. -
Updated the Docker host configuration to expose port 443 to enable access to Adobe 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.
-
-
app/etc/env.php
file exists. -
-
v1.1.2
Release date: September 9, 2020
v1.1.1
Release date: August 5, 2020
-
-
ps: command not found
errors. -
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
andwith-mariadb-conf
. See Service configuration options. -
./vendor/bin/ece-docker build:compose --db --with-entrypoint
./vendor/bin/ece-docker build:compose --db --mariadb-conf
v1.1.0
Release date: June 25, 2020
-
-
-
-
-
Varnish—Now Varnish is the default cache when you deploy Adobe Commerce in a Cloud Docker environment using a supported version of the Cloud application template. See Varnish container.
-
Added the
--no-varnish
option to skip Varnish service installation when you generate the Cloud Docker configuration file. -
-
Added the support for the MySQL database. Now, you can configure the Cloud Docker environment with either MariaDB or MySQL. See Service configuration options.
-
Added the ability to set the increment and offset settings for database replication when you generate the Docker compose file. See Service containers.
-
-
-
Added support for PHP 7.4. Fix submitted by Mohanela Murugan from Zilker Technology
-
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 Customize PHP settings. Fix submitted by Mathew Beane from Zilker Technology. -
Added a container health check. Fix submitted by Visanth Sampath from Zilker Technology.
-
-
-
-
Added support for Elasticsearch 6.8, 7.2, 7.5, and 7.6.
-
Added the ability to customize the Elasticsearch container configuration 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 Adobe Commerce versions 2.3.5 and earlier.
-
-
-
-
-
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. Fix submitted by Mathew Beane from Zilker Technology. -
-
bin/magento-docker flush-redis
bin/magento-docker flush-varnish
.vendor/bin/ece-docker build:compose --no-varnish
.vendor/bin/ece-docker build:compose --es-env-var
.vendor/bin/ece-docker build:compose --no-es
./vendor/bin/ece-docker build:compose --db <mysql-version-number> --db-image mysql
./vendor/bin/ece-docker build:compose --host=<hostname> --port=<port-number>
.vendor/bin/ece-docker build:compose --mode developer --sync-engine native --with-xdebug
-
-
-
-
ece-docker build:compose
command to fail if the configuration included Blackfire.io. Fix submitted by G Arvind from Zilker Technology. -
-
build:compose
operation failed if themagento.app.yaml
file specified multiple database users. Fix submitted by G Arvind from Zilker Technology. -
rsyslog
from the Cloud Docker for Commerce PHP containers to resolve compatibility issues that caused warning notifications during deployment. Cloud Docker does not use the rsyslog utility.
v1.0.0
Release date: Feb 5, 2020