magento-ecg-team/magento2-docker

Magento 2 Docker-compose project

This docker-compose project use few containers:

• nginx
• php7.3-fpm
• mariadb
• mailhog

Docker-compose will clone magento repo, run composer install and magento install All those could be changed in .env file

Domain name http://mage.localhost SSH root pass: 123123q You may want to configure your code changes/sync using ssh connection

build

docker-compose build

run

docker-compose up

connect using ssh

ssh -p 2222 root@localhost

clean old ssh hash

ssh-keygen -R [localhost]:2222

clean

docker-compose down

hard clean

docker-compose down --rmi all -v

super hard clean

docker rm -f $(docker ps -q -a)

docker rmi -f $(docker images -q)

magento2-docker's Issues

Directories with root owner are generated during Magento2 installation

Workaround added.

Moving environment variables from docker files to environment

For now environment variables, such as:

• MySQL settings
• path to Magento2 directory
• Magento2 installation options
• Magento 2 version
• etc.

are hardcoded into files with docker instructions. We should create separate environment file(s), .env for example, to keep environment variables in one place.

Specifying branch 2.2 in magento2-docker/php/Dockerfile

Current docker compose configuration set up for Magento version 2.2. By default git clone command gets latest branch, which is 2.3 for now.

PHP service container startup is broken

Most likely cause of the issue is using of CMD instruction in php service Dockerfile.
My thouths that this CMD instruction may conflict with CMD instruction from php-fpm image.
From Dockerfile CMD reference:

There can only be one CMD instruction in a Dockerfile. If you list more than one CMD then only the last CMD will take effect.

For this time workaround was added.

Alpine images should be in use

We should change common images to alpine to make containers more lightweight:

• php-fpm image
• nginx image
• db image