wunderio/image-fuzzy-alpine-mariadb

image-fuzzy-alpine-mariadb's Issues

Maybe it doesn't make sense to instal_db before a custom my.cnf is installed

Extending this image with a new my.cnf, means that the mysql_install_db needs to be repeated (depending on the changes to the conf.)

Should we be installing in this image? Should we accept a base image that does not itself produce a "running container"?

For example, this image used to extend alpine-mariadb, but now just steals most of the Dockerfile, instead if re-creating the db.

Point logs to somewhere Docker can read them

Current attempt doesn't work and is disable. Consider also setting the default log location be a volume in case only we can do is duplicate the logs to syslog so we should try to avoid making the container huge with logs and instead make the volume location a separate volume. This might be helpful https://mariadb.com/kb/en/mariadb/overview-of-mariadb-logs/

Mariadb fails to start

The following error occurs when trying to run this image:

2016-05-06 05:45:58 7fb318858da8  InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory.

If you chown the var/lib/mysql then it works fine:

$/> chown -R mysql:mysql /var/lib/mysql

Handle container stopping discretely

Currently it doesn't stop and just times out eventually.

Update MariaDB to 10.1.20

https://pkgs.alpinelinux.org/packages?name=mariadb&branch=&repo=&arch=&maintainer=