Mark Shust

Mark Shust

Magento 2 speed, security permissions & docker

Speed security permissions & docker

Note that this blog post was originally written by myself on Mage Inferno’s blog, which no longer exists. Many old user comments have been lost, but this post won’t be!

We hope you’ve enjoyed (and continue to enjoy) our Docker images for Magento 2 and related Docker Compose setup. Mage Inferno believes Docker is the future of web deployment development & deployment pipelines. While our Docker images generally work really well, working with Docker on OS X has posed it’s own sets of issues and limitations.

Native Performance

If you develop on OS X with Docker and use the default VirtualBox filesystem (vboxfs), you will have a pretty horrible experience if you mount remote fileshares, especially with the many folders & files included in the Magento 2 architecture. This leads most people to run either a filesystem hack or a solution with custom NFS fileshare capabilities, such as Dinghy or DLite.

Dinghy is something that we initially suggested to use in our original Magento 2 Development with Docker on OS X post, and it has proved to be a pretty great tool that also includes a DNS server and HTTP proxy. That said, some have questioned the stack and raised their own sets of concerns with having to implement yet another tool besides Docker, or not being able to use the Docker Toolbox directly with these third-party tools. Dinghy and Docker Toolbox also have a very long startup process, and need to request Admin access to mount remote fileshares (which also comes with it’s own set of security concerns).

Permission Errors

Magento 2 comes out of the box with very rigorous, locked-down set of security permissions. Magento suggests running their software with a new magento user and they also have implemented additional application-level security controls. As you can see with the infamous permissions issue #2412, the decision to implement application-level security controls has backfired within the community, and is generally regarded as the number one impediment for a new user installing Magento 2.

The path of least resistance is to remove application-level security controls, which it does appear Magento is in the process of merging in & resolving. However, this changeset does not appear to be merged into the most recent version of Magento at the time of this post (2.0.4).

Welcome to Docker for Mac

Luckily, the ecosystem is progressing, and now there is a better way.

We’ve recently received our beta invite to the beta for Docker for Mac, and here is our general consensus:

Oh snap

You can read all of the benefits yourself on the Features Overview page, but here are some key bullet points:

The “magento” User

Until issue #2412 is resolved, we are recommending to all users of Magento 2 to not implement or use the newly recommended magento user. Due to the inability for multiple software packages to properly communicate with each other and work in tandem (because of the implemented application-level security controls), it is practically impossible to get Magento 2 running with the new magento user, especially when implementing a setup such as our recommended Nginx + PHP-FPM stack.

We’ve updated all of our Docker images to only run with the www-user user/group, updated all files/folders to be owned by www-user user/group, and removed the magento user completely from our build scripts. We don’t believe the are any inherent security problems at the present time with running this type of ownership setup, and hoping as soon as issue #2412 is resolved, we can reimplement the magento user ownerships on files & folders.

New Docker Images

Mage Inferno’s Docker images now have over 10,000 pulls! We thank the community for the overwhelming feedback we’ve received from being the number one Magento 2 Docker images available on DockerHub. We strongly believe that it is still the easiest way to get started with Magento 2 development, and will continue to be for some time.

Mage Inferno - Docker Hub
View all Mage Inferno images at Docker Hub

In honor of hitting our 10,000 pull milestone, we are releasing a new set of Docker images, which will resolve all of the security and permission problems that have occurred in the past.

You can use our Docker images on the current Docker Toolbox, or if you already have access to the new Docker for Mac, use that for better performance.

3 Simple Steps

It’s so easy to get Magento 2 installed today with Docker, Docker Compose and our container images.

Step 1: Create docker-compose.yml file:

(also available on GitHub at

# Mage Inferno Docker Compose (
# Version 4.1.0

  image: mageinferno/magento2-nginx:1.9.14-0
    - phpfpm
    - db
    - appdata
    - 8000:80

  image: tianon/true
    - /srv/www
#    - ~/.composer:/var/www/.composer
#    - ./www/app/code:/srv/www/app/code

  image: mageinferno/magento2-php:7.0.5-fpm-0
    - db
    - appdata

  image: mariadb:10.1.13
    - dbdata
    - 8001:3306
    - MYSQL_ROOT_PASSWORD=magento2
    - MYSQL_DATABASE=magento2
    - MYSQL_USER=magento2
    - MYSQL_PASSWORD=magento2

  image: tianon/true
    - /var/lib/mysql

  image: mageinferno/magento2-php:7.0.5-fpm-0
  command: /usr/local/bin/mage-setup
    - db
    - appdata
    - M2SETUP_DB_HOST=db
    - M2SETUP_DB_NAME=magento2
    - M2SETUP_DB_USER=magento2
    - M2SETUP_DB_PASSWORD=magento2
    - M2SETUP_BASE_URL=http://m2.localhost:8000/
    - M2SETUP_ADMIN_USER=magento2
    - M2SETUP_VERSION=2.0.5

Step 2: Install Magento 2

docker-compose run --rm setup

Step 3: Start Magento 2 Application

docker-compose up -d app


Once the Docker container images initially download, the setup is 100% automated and you’ll be up & running in no time. Update the environment variables to set your desired options (for instance, to install sample data, set M2SETUP_USE_SAMPLE_DATA to true), run a couple commands, and you are good to go.

Here’s to another 10,000 pulls!