Ramblings of Daniel Graziotin



As of Docker for Mac v1.12.0, there is no need for using my Docker images anymore. Thanks for the support!


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

Some info about osx-docker-mysql:

  • It is based on phusion/baseimage:latest instead of ubuntu:trusty.
  • It works flawlessy regardless of using boot2docker standalone or with Vagrant. You will need to set three enrironment varibles, though.
  • It fixes OS X related write permission errors for MySQL
  • It lets you mount OS X folders with write support as volumes for
    • The database
  • If  CREATE_MYSQL_BASIC_USER_AND_DB="true", it creates a default database and user with permissions to that database
  • It is documented for less advanced users (like me)


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

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

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


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 MySQL docker image

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

At [boot2docker ip] you should be able to connect to MySQL.

Loading your custom MySQL files

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

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

Environment description

The /mysql folder

MySQL is configured to serve the files from the  /mysql folder, which is a symbolic link to  /var/lib/mysql. In osx-docker-mysql, the MySQL user  mysql has full write permissions to the  mysql folder.


MySQL runs as user  mysql and group  staff.

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:

You will see an output like the following:

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 environment variable  CREATE_MYSQL_BASIC_USER_AND_DB is true; or
  • Any of the  MYSQL_USER_* variable (explained below) is true The user is called  user and has as password  password.

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

  • MYSQL_ADMIN_PASS="mypass" will use your given MySQL password for the  admin user instead of the random one.
  • CREATE_MYSQL_BASIC_USER_AND_DB="true" will create the user  user with db  db and password  password. Not needed if using one of the following three  MYSQL_USER_* variables
  • MYSQL_USER_NAME="daniel" will use your given MySQL username instead of  user
  • MYSQL_USER_DB="supercooldb" will use your given database name instead of  db
  • MYSQL_USER_PASS="supersecretpassword" will use your given password instead of  password
  • 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

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

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


  • Unfortunately, I couldn’t get this to work on OSX.
    The mounted folder is automatically created but it doesn’t contain any files although the logging suggests that everything is fine:

    We also created
    A database called ‘spotweb’ and
    a user called ‘spotweb’ with password ‘spotweb’
    ‘spotweb’ has full access on ‘spotweb’

    I’m trying to set up spotweb per my own instructions here: https://github.com/andyverbunt/docker-spotweb

    but with a locally mounted folder.

Ramblings of Daniel Graziotin

About Author


Dr. Daniel Graziotin received his PhD in computer science, software engineering at the Free University of Bozen-Bolzano, Italy. His research interests include human aspects in empirical software engineering with psychological measurements, Web engineering, and open science. He researches, publishes, and reviews for venues in software engineering, human-computer interaction, and psychology. Daniel is the founder of the psychoempirical software engineering discipline and guidelines. He is associate editor at the Journal of Open Research Software, academic editor at the Research Ideas and Outcomes (RIO) journal, and academic editor at the Open Communications in Computer Science journal. He is the local coordinator of the Italian Open science local group for the Open Knowledge Foundation. He is a member of ACM, SIGSOFT, and IEEE.