Running Magento 2 on our appserver.io Docker container provides some advantages because some of the requirements that usually needs manual tweaks will be already set-up for you, like
So installing Magento 2 in an appserver.io Docker container needs basically five steps.
Download and install Docker for your system.
If you already have a running Docker installation, you can skip this step and proceed with Step 2.
If you already have MySQL running on your system, you have to stop this temporarily, because port
3306
will already be in use and the Docker container can not be started.
Starting a MySQL container with Docker is pretty simple. Open your commandline and execute the following command
MacBook-Pro:~ docker run -d \
--name mysql-5.6 -p127.0.0.1:3306:3306 \
-e MYSQL_ROOT_HOST=% \
-e MYSQL_ROOT_PASSWORD=appserver.i0 \
mysql/mysql-server:5.6
This downloads a MySQL 5.6 Docker image and starts a container with MySQL listen on port
127.0.0.1:3306
of your local machine.
If you already have a webserver running that listens either to one of the ports
80
and443
you'll also have to stop it temporarly.
Beside the MySQL container, we need a appserver.io container that runs the Magento 2 instance. Again, open your commandline, if you've already closed it, and execute the following command
MacBook-Pro:~ docker run -d \
-p127.0.0.1:80:80 \
-p127.0.0.1:443:443 \
-v /Users/wagnert/Workspace:/root/Workspace \
--name appserver-1.1.4-magento \
--link mysql-5.6:mysql \
appserver/dist:1.1.4
This downlaods the latest stable appserver.io image and starts a container with the webserver and
PHP-FPM listening to the ports 127.0.0.1:80
and 127.0.0.1:443
. Additionally it links the MySQL
container, that we've created in Step 2 and makes it
available as service with the name mysql
.
Beside the possiblity to copy the files to the webserver root directory, appserver.io also supports a PHAR based deployment. This allows us to deploy Magento 2 by downloading the sources - including all composer dependencies - as a PHAR archive and copy it to the deployment directory inside the Docker container. To do this, execute the following lines on the commandline
MacBook-Pro:~ docker exec appserver-1.1.4-magento bash -c \
"wget http://apps.appserver.io/magento2/magento2-latest.phar \
-O /opt/appserver/deploy/magento2-latest.phar"
MacBook-Pro:~ docker exec appserver-1.1.4-magento bash -c \
"touch /opt/appserver/deploy/magento2-latest.phar.dodeploy"
Now wait until appserver.io has deployed the Magento 2 sources. To check if everything is ready, execute the following command several times and check the output
MacBook-Pro:~ wagnert$ docker exec appserver-1.1.4-magento bash -c "ls -l /opt/appserver/deploy"
total 195588
-rw-r--r-- 1 root root 4384 Jun 9 07:21 README.md
-rw-r--r-- 1 root root 200269499 Jun 9 0017 magento2-latest.phar
-rw-rw-r-- 1 root root 44 Jun 10 15:23 magento2-latest.phar.deployed
When the file magento2-latest.phar.deploying
changed to magento2-latest.phar.deployed
Magento 2
has successfully been deployed.
The Magento 2 deployment process could take up to 1 minute, depending on your hardware!
The final step is the Magento 2 installation and restart the CRON. This can either be done by running the setup in your browser or on the commandline by executing the following lines
MacBook-Pro:~ docker exec mysql-5.6 bash -c "mysql -uroot -pappserver.i0 --execute='CREATE DATABASE magento2'"
MacBook-Pro:~ docker exec appserver-1.1.4-magento bash -c \
"bin/php webapps/magento2-latest/bin/magento setup:install \
--backend-frontname=admin \
--db-host=mysql \
--db-password=appserver.i0 \
--admin-user=appserver \
--admin-firstname=Foo \
--admin-lastname=Bar \
--admin-password=appserver.i0 \
--admin-email=info@appserver.io"
MacBook-Pro:~ docker exec mysql-5.6 bash -c "supervisorctl restart appserver-watcher'"
Finally, user your browser to open the Magento 2 frontend or
backend logging in with username appserver
and
password appserver.i0
.
That's it - have fun!
Please note that by clicking "Load Comments", your browser will establish a connection with servers from Disqus.
For more information, please visit our privacy statement.