From 61e73552878ec910a0a929340dda86c6e6721f98 Mon Sep 17 00:00:00 2001 From: Frank Sachsenheim Date: Wed, 30 Sep 2015 23:41:02 +0200 Subject: [PATCH] Adds a note about docker-entrypoint-initdb.d refers to 14f1655 Signed-off-by: Frank Sachsenheim --- mysql/content.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/mysql/content.md b/mysql/content.md index 13fa72b8a..65a282f5d 100644 --- a/mysql/content.md +++ b/mysql/content.md @@ -92,6 +92,10 @@ Do note that there is no need to use this mechanism to create the root superuser This is an optional variable. Set to `yes` to allow the container to be started with a blank password for the root user. *NOTE*: Setting this variable to `yes` is not recommended unless you really know what you are doing, since this will leave your MySQL instance completely unprotected, allowing anyone to gain complete superuser access. +# Initializing a fresh instance + +When a container is started for the first time, a new database `mysql` will be initialized with the provided configuration variables. Furthermore, it will execute `.sh`- and `.sql`-files that are found in `/docker-entrypoint-initdb.d`. You can easily populate your %%REPO%% services by [mounting a SQL dump into that directory](https://docs.docker.com/userguide/dockervolumes/#mount-a-host-file-as-a-data-volume) and provide [custom images](https://docs.docker.com/reference/builder/) with contributed data. + # Caveats ## Where to Store Data