I'm finding an issue with mariadb:latest docker image, where upon startup the process gets stuck at mysql_install_db at the point logfiles are being created:

*_Initializing database
2016-11-02 6:40:46 140203338909632 [Note] /usr/sbin/mysqld (mysqld 10.1.16-MariaDB-1~jessie) starting as process 60 ...
2016-11-02 6:40:46 140203338909632 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-11-02 6:40:46 140203338909632 [Note] InnoDB: The InnoDB memory heap is disabled
2016-11-02 6:40:46 140203338909632 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-11-02 6:40:46 140203338909632 [Note] InnoDB: Memory barrier is not used
2016-11-02 6:40:46 140203338909632 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-11-02 6:40:46 140203338909632 [Note] InnoDB: Using Linux native AIO
2016-11-02 6:40:46 140203338909632 [Note] InnoDB: Using SSE crc32 instructions
2016-11-02 6:40:46 140203338909632 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2016-11-02 6:40:46 140203338909632 [Note] InnoDB: Completed initialization of buffer pool
2016-11-02 6:40:46 140203338909632 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2016-11-02 6:40:46 140203338909632 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2016-11-02 6:40:46 140203338909632 [Note] InnoDB: Database physically writes the file full: wait...
2016-11-02 6:40:46 140203338909632 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2016-11-02 6:40:48 140203338909632 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB_*

Looking at the container, you can see the processes stuck:

*_root@lucky3-db-pauvc:/# ps -ax
PID TTY STAT TIME COMMAND
1 ? Ss 0:00 /bin/bash /usr/local/bin/docker-entrypoint.sh mysqld
33 ? S 0:00 /bin/sh /usr/bin/mysql_install_db --datadir=/var/lib/mysql/ --rpm
58 ? S 0:00 /bin/sh /usr/bin/mysql_install_db --datadir=/var/lib/mysql/ --rpm
60 ? Dl 0:00 /usr/sbin/mysqld --lc-messages-dir=/usr/share/mysql/english/.. --bootstrap --basedir=/usr --datadir=/var/lib/mysql/ --log-warnings=0 --enforce-storage-engine= --max_allowed_packet=8M –
72 ? Ss 0:00 /bin/sh -i -c TERM=xterm /bin/sh
83 ? S 0:00 /bin/sh
84 ? S 0:00 bash
85 ? R+ 0:00 ps -ax _*

/var/lib/mysql is mapped correctly to a glusterfs volume, which is good, and usuable if using docker image mysql:latest

[root@master1 .bricks]# gluster volume status myapp-db-develop
Status of volume: myapp-db-develop
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick master1.mycluster.com:/srv/.br
icks/myapp-db-develop 49392 0 Y 28720
Brick master2.mycluster.com:/srv/.br
icks/myapp-db-develop 49395 0 Y 16478
Brick master3.mycluster.com:/srv/.br
icks/myapp-db-develop 49399 0 Y 18142
Self-heal Daemon on localhost N/A N/A Y 29240
Self-heal Daemon on master2.mycluster.com N/A N/A Y 2779
Self-heal Daemon on master3.mycluster.com N/A N/A Y 22718

Task Status of Volume myapp-db-develop
------------------------------------------------------------------------------
There are no active volume tasks

Running a mysql:latest docker image works as expected.