ERROR: 1049 Unknown database 'test'

[BarnumD]

Docker 1.9.1 on Ubuntu 14:
docker run --name some-mariadb -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mariadb:10.1

Error:
ERROR: 1049 Unknown database 'test'

Extended Info:
Initializing database
2016-02-01 20:06:04 139864276592576 [Note] /usr/sbin/mysqld (mysqld 10.1.11-MariaDB-1jessie) starting as process 50 ...
2016-02-01 20:06:04 139864276592576 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-02-01 20:06:04 139864276592576 [Note] InnoDB: The InnoDB memory heap is disabled
2016-02-01 20:06:04 139864276592576 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-02-01 20:06:04 139864276592576 [Note] InnoDB: Memory barrier is not used
2016-02-01 20:06:04 139864276592576 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-02-01 20:06:04 139864276592576 [Note] InnoDB: Using Linux native AIO
2016-02-01 20:06:04 139864276592576 [Note] InnoDB: Using SSE crc32 instructions
2016-02-01 20:06:04 139864276592576 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2016-02-01 20:06:04 139864276592576 [Note] InnoDB: Completed initialization of buffer pool
2016-02-01 20:06:04 139864276592576 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2016-02-01 20:06:04 139864276592576 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2016-02-01 20:06:04 139864276592576 [Note] InnoDB: Database physically writes the file full: wait...
2016-02-01 20:06:05 139864276592576 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2016-02-01 20:06:05 139864276592576 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2016-02-01 20:06:05 139864276592576 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2016-02-01 20:06:05 139864276592576 [Warning] InnoDB: New log files created, LSN=45883
2016-02-01 20:06:05 139864276592576 [Note] InnoDB: Doublewrite buffer not found: creating new
2016-02-01 20:06:05 139864276592576 [Note] InnoDB: Doublewrite buffer created
2016-02-01 20:06:05 139864276592576 [Note] InnoDB: 128 rollback segment(s) are active.
2016-02-01 20:06:05 139864276592576 [Warning] InnoDB: Creating foreign key constraint system tables.
2016-02-01 20:06:05 139864276592576 [Note] InnoDB: Foreign key constraint system tables created
2016-02-01 20:06:05 139864276592576 [Note] InnoDB: Creating tablespace and datafile system tables.
2016-02-01 20:06:05 139864276592576 [Note] InnoDB: Tablespace and datafile system tables created.
2016-02-01 20:06:05 139864276592576 [Note] InnoDB: Waiting for purge to start
2016-02-01 20:06:05 139864276592576 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-76.0 started; log sequence number 0
2016-02-01 20:06:05 139863475091200 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-02-01 20:06:07 140263219955648 [Note] /usr/sbin/mysqld (mysqld 10.1.11-MariaDB-1jessie) starting as process 78 ...
2016-02-01 20:06:07 140263219955648 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-02-01 20:06:07 140263219955648 [Note] InnoDB: The InnoDB memory heap is disabled
2016-02-01 20:06:07 140263219955648 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-02-01 20:06:07 140263219955648 [Note] InnoDB: Memory barrier is not used
2016-02-01 20:06:07 140263219955648 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-02-01 20:06:07 140263219955648 [Note] InnoDB: Using Linux native AIO
2016-02-01 20:06:07 140263219955648 [Note] InnoDB: Using SSE crc32 instructions
2016-02-01 20:06:07 140263219955648 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2016-02-01 20:06:07 140263219955648 [Note] InnoDB: Completed initialization of buffer pool
2016-02-01 20:06:07 140263219955648 [Note] InnoDB: Highest supported file format is Barracuda.
2016-02-01 20:06:07 140263219955648 [Note] InnoDB: 128 rollback segment(s) are active.
2016-02-01 20:06:07 140263219955648 [Note] InnoDB: Waiting for purge to start
2016-02-01 20:06:07 140263219955648 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-76.0 started; log sequence number 1616799
2016-02-01 20:06:07 140262424676096 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-02-01 20:06:10 140263203276736 [Note] /usr/sbin/mysqld (mysqld 10.1.11-MariaDB-1~jessie) starting as process 107 ...
2016-02-01 20:06:10 140263203276736 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-02-01 20:06:10 140263203276736 [Note] InnoDB: The InnoDB memory heap is disabled
2016-02-01 20:06:10 140263203276736 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-02-01 20:06:10 140263203276736 [Note] InnoDB: Memory barrier is not used
2016-02-01 20:06:10 140263203276736 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-02-01 20:06:10 140263203276736 [Note] InnoDB: Using Linux native AIO
2016-02-01 20:06:10 140263203276736 [Note] InnoDB: Using SSE crc32 instructions
2016-02-01 20:06:10 140263203276736 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2016-02-01 20:06:10 140263203276736 [Note] InnoDB: Completed initialization of buffer pool
2016-02-01 20:06:10 140263203276736 [Note] InnoDB: Highest supported file format is Barracuda.
2016-02-01 20:06:10 140263203276736 [Note] InnoDB: 128 rollback segment(s) are active.
2016-02-01 20:06:10 140263203276736 [Note] InnoDB: Waiting for purge to start
2016-02-01 20:06:10 140263203276736 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-76.0 started; log sequence number 1616809
2016-02-01 20:06:10 140262407898880 [Note] InnoDB: Dumping buffer pool(s) not yet started
ERROR: 1049 Unknown database 'test'
2016-02-01 20:06:10 140263203276736 [ERROR] Aborting

[BarnumD]

Was trying to follow instructions under 'Start a mariadb server instance' on dockerhub but got the above error. Had to add MYSQL_DATABASE=Somedatabase -e MYSQL_ROOT_PASSWORD=somepassword in order for it to work.

[jmatsushita]

I confirm that I'm also encountering this bug when trying to use both MYSQL_ROOT_PASSWORD and MYSQL_DATABASE.

There's also another report here: https://mariadb.com/kb/en/mariadb/mariadb-10112-mysql_install_db-aborts-on-unkown-file-test/

This makes the docker image unusable for me.

[stuartz]

@jmatsushita The post that you mentioned is one I put up. Since then I have been using a variation of the official docker/mariadb for a cluster. I have posted thoughts and utilities at https://github.com/stuartz/mariadb-cluster. Most of it is up to date, but I have made some changes that I have not updated yet. It does abort, but starts up again. One tricky area is putting the data in a volume for persistence. I have had issues with SST transfer of clearing files to transfer and failing because they still exist on the cached layer. In the case where I needed to do a full SST, I deleted the volume and restarted fresh. Performance over the mysql 5.1 server we had is outstanding.

For connecting nodes on AWS, I had trouble with binding the listener and went with secured weave for ssl connections between AWS and our local node.

[cgaubuchon]

Seems that if I run docker-compose run command with sudo that it installs and connects as planned.

[jonathandemoor]

Also had the same issue, I fixed it by removing my local mariadb image and pulling it again.