As of [Docker for Mac v1.12.0](https://docs.docker.com/engine/installation/mac/), there is no need for using my Docker images anymore. Thanks for the support!


Out-of-the-box LAMP+phpMyAdmin Docker image that *just works* on Mac OS X. 
Including write support for mounted volumes (Website, MySQL).
No matter if using the official boot2docker or having Vagrant in the stack, as well.

osx-docker-lamp, which is known as dgraziotin/lamp in the Docker Hub, is a fork of tutumcloud/tutum-docker-lamp, which is an “Out-of-the-box LAMP image (PHP+MySQL) for Docker”.

osx-docker-lamp does what tutumcloud/tutum-docker-lamp, plus:


If using Vagrant, please see the extra steps in the next subsection.

If you need to create a custom image youruser/lamp, execute the following command from the osx-docker-lamp source folder:

docker build -t youruser/lamp .

If you wish, you can push your new image to the registry:

docker push youruser/lamp

Otherwise, you are free to use dgraziotin/lamp as it is provided. Remember first to pull it from the Docker Hub:

docker pull dgraziotin/lamp


If, for any reason, you would rather use Vagrant (I suggest using AntonioMeireles/boot2docker-vagrant-box), you need to add the following three variables when running your box:

-VAGRANT_OSX_MODE="true" for enabling Vagrant-compatibility -DOCKER_USER_ID=$(id -u) for letting Vagrant use your host user ID for mounted folders -DOCKER_USER_GID=$(id -g) for letting Vagrant use your host user GID for mounted folders

See the Environment variables section for more options.

Running your LAMP docker image

If you start the image without supplying your code, e.g.,

docker run -t -i -p 80:80 -p 3306:3306 --name osxlamp dgraziotin/lamp

At http://[boot2docker ip, e.g.,] you should see an “Hello world!” page.

At http://[boot2docker ip]/phpmyadmin you should see a running phpMyAdmin instance.

Loading your custom PHP application

In order to replace the Hello World application that comes bundled with this docker image, my suggested layout is the following:

The app folder should contain the root of your PHP application.

Run the following code from within the Project name folder.

docker run -i -t -p "80:80" -p "3306:3306" -v ${PWD}/app:/app --name yourwebapp dgraziotin/lamp

Test your deployment:

http://[boot2docker ip]
http://[boot2docker ip]/phpmyadmin

If you wish to mount a MySQL folder locally, so that MySQL files are saved on your OS X machine, run the following instead:

docker run -i -t -p "80:80" -p "3306:3306" -v ${PWD}/mysql:/var/lib/mysql -v ${PWD}/app:/app --name yourwebapp dgraziotin/lamp

The MySQL database will thus become persistent at each subsequent run of your image.

Environment description

The /app folder

Apache is configured to serve the files from the /app folder, which is a symbolic link to /var/www/html. In osx-docker-lamp, the apache user www-data has full write permissions to the appfolder.


Apache is pretty much standard in this image. It is configured to serve the Web app at app as / and phpMyAdmin as /phpmyadmin. Mod rewrite is enabled.

Apache runs as user www-data and group staff. The write support works because the user www-data is configured to have the same user id as the one employed by boot2docker (1000).


The latest version of phpMyAdmin is grabbed from sourceforge and installed in the folder /var/www/phpmyadmin.

PhpMyAdmin can be reached from http://[boot2docker ip]/phpmyadmin. Only the users admin and user can access phpMyAdmin.

At your convenience, a not-so-random blowfish_secret is stored in phpMyAdmin configuration, which is at /var/www/phpmyadmin/config.inc.php


MySQL runs as user www-data, as well. This is not the best settings for production. However, this is needed for proving write support to mounted volumes under Mac OS X.

The three MySQL users

The bundled MySQL server has two users, that are root and admin, and an optional third user user.

The root account comes with an empty password, and it is for local connections (e.g., using some code). The root user cannot remotely access the database (and the container).

However, the first time that you run your container, a new user admin with all root privileges will be created in MySQL with a random password.

To get the password, check the logs of the container by running:

docker logs [name or id, e.g., mywebsite]

You will see an output like the following:

You can now connect to this MySQL Server using:

    mysql -uadmin -p47nnf4FweaKu -h<host> -P<port>

Please remember to change the above password as soon as possible!
MySQL user 'root' has no password but only allows local connections

In this case, 47nnf4FweaKu is the password allocated to the admin user.

Finally, an optional a user called user with password password can be created for your convenience either when:

The user user has full privileges on a database called db, which is also created for your convenience. As with the admin user, the user user can access the MySQL server from any host (%). The user name, password, and database name can be changed using the the MYSQL_USER_*variables, explained below.

Environment variables

Set these variables using the -e flag when invoking the docker client.

docker run -i -t -p "80:80" -p "3306:3306" -v ${PWD}/app:/app -e MYSQL_ADMIN_PASS="mypass" --name yourwebapp dgraziotin/lamp

Please note that the MySQL variables will not work if an existing MySQL volume is supplied.