From b2494955c25f63b3979bb77c55ab591f42f2a8c1 Mon Sep 17 00:00:00 2001 From: Alberto Roura Date: Fri, 7 Oct 2022 11:47:21 +1000 Subject: [PATCH 1/3] Typo when referring to pre-existing db folder --- mariadb/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mariadb/README.md b/mariadb/README.md index 02e1eb7e3f75..be26d29822df 100644 --- a/mariadb/README.md +++ b/mariadb/README.md @@ -277,7 +277,7 @@ See [the "Official Images" FAQ](https://github.com/docker-library/faq#healthchec ## Usage against an existing database -If you start your `mariadb` container instance with a data directory that already contains a database (specifically, a `mysql` subdirectory), no environment variables that control initialization will be needed or examined, and no pre-existing databases will not be changed. The only exception is the non-default `MARIADB_AUTO_UPGRADE` environment variable, that might cause `mysql_upgrade`/`mariadb-upgrade` to run, which might change the system tables. +If you start your `mariadb` container instance with a data directory that already contains a database (specifically, a `mysql` subdirectory), no environment variables that control initialization will be needed or examined, and no pre-existing databases will be changed. The only exception is the non-default `MARIADB_AUTO_UPGRADE` environment variable, that might cause `mysql_upgrade`/`mariadb-upgrade` to run, which might change the system tables. ## Creating database dumps From 8693729bd084e92f905cbce13ca81df866ea6a43 Mon Sep 17 00:00:00 2001 From: Alberto Roura Date: Fri, 7 Oct 2022 15:42:05 +1000 Subject: [PATCH 2/3] Update README.md --- mariadb/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mariadb/README.md b/mariadb/README.md index be26d29822df..02e1eb7e3f75 100644 --- a/mariadb/README.md +++ b/mariadb/README.md @@ -277,7 +277,7 @@ See [the "Official Images" FAQ](https://github.com/docker-library/faq#healthchec ## Usage against an existing database -If you start your `mariadb` container instance with a data directory that already contains a database (specifically, a `mysql` subdirectory), no environment variables that control initialization will be needed or examined, and no pre-existing databases will be changed. The only exception is the non-default `MARIADB_AUTO_UPGRADE` environment variable, that might cause `mysql_upgrade`/`mariadb-upgrade` to run, which might change the system tables. +If you start your `mariadb` container instance with a data directory that already contains a database (specifically, a `mysql` subdirectory), no environment variables that control initialization will be needed or examined, and no pre-existing databases will not be changed. The only exception is the non-default `MARIADB_AUTO_UPGRADE` environment variable, that might cause `mysql_upgrade`/`mariadb-upgrade` to run, which might change the system tables. ## Creating database dumps From 644cf49d8f3d9d6fdc9f6e81f788815a7d2960e9 Mon Sep 17 00:00:00 2001 From: Alberto Roura Date: Fri, 7 Oct 2022 15:42:28 +1000 Subject: [PATCH 3/3] Update content.md --- mariadb/content.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mariadb/content.md b/mariadb/content.md index d14943b01df4..dd8746491a77 100644 --- a/mariadb/content.md +++ b/mariadb/content.md @@ -198,7 +198,7 @@ See [the "Official Images" FAQ](https://github.com/docker-library/faq#healthchec ## Usage against an existing database -If you start your `%%IMAGE%%` container instance with a data directory that already contains a database (specifically, a `mysql` subdirectory), no environment variables that control initialization will be needed or examined, and no pre-existing databases will not be changed. The only exception is the non-default `MARIADB_AUTO_UPGRADE` environment variable, that might cause `mysql_upgrade`/`mariadb-upgrade` to run, which might change the system tables. +If you start your `%%IMAGE%%` container instance with a data directory that already contains a database (specifically, a `mysql` subdirectory), no environment variables that control initialization will be needed or examined, and no pre-existing databases will be changed. The only exception is the non-default `MARIADB_AUTO_UPGRADE` environment variable, that might cause `mysql_upgrade`/`mariadb-upgrade` to run, which might change the system tables. ## Creating database dumps