You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,9 +56,7 @@ The architectures supported by this image are:
56
56
57
57
## Application Setup
58
58
59
-
If you didn't set a password during installation, (see logs for warning) use
60
-
`mariadb-admin -u root -p<PASSWORD>`
61
-
to set one at the docker prompt...
59
+
Root via localhost (docker exec) no longer requires a password according to [upstream behavior](https://mariadb.com/docs/server/security/user-account-management/authentication-from-mariadb-10-4), if you didn't set a root password for remote access during the initial start follow the instructions in the container log.
62
60
63
61
NOTE changing any of the MYSQL_ variables after the container has set up the initial databases has no effect, use the mysqladmin tool or cli to make changes.
64
62
@@ -103,10 +101,10 @@ This will have the same effect as setting the `REMOTE_SQL` environment variable.
103
101
If user databases are not in a healthy state (sometimes caused by a failed upgrade), it may be remedied by running:
104
102
105
103
```shell
106
-
mariadb-check -u root -p<PASSWORD> -c -A # check all databases for errors
107
-
mariadb-check -u root -p<PASSWORD> -r -A # repair all databases
108
-
mariadb-check -u root -p<PASSWORD> -a -A # analyze all databases
109
-
mariadb-check -u root -p<PASSWORD> -o -A # optimize all databases
104
+
mariadb-check -c -A # check all databases for errors
105
+
mariadb-check -r -A # repair all databases
106
+
mariadb-check -a -A # analyze all databases
107
+
mariadb-check -o -A # optimize all databases
110
108
```
111
109
112
110
After running the above commands, you may need to run the upgrade command again.
@@ -116,7 +114,7 @@ After running the above commands, you may need to run the upgrade command again.
116
114
When this container initializes, if `MYSQL_ROOT_PASSWORD` is set an upgrade check will run. If an upgrade is required the log will indicate the need stop any services that are accessing databases in this container, and then run the command:
Copy file name to clipboardExpand all lines: readme-vars.yml
+6-8Lines changed: 6 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -38,9 +38,7 @@ nonroot_supported: true
38
38
# application setup block
39
39
app_setup_block_enabled: true
40
40
app_setup_block: |
41
-
If you didn't set a password during installation, (see logs for warning) use
42
-
`mariadb-admin -u root -p<PASSWORD>`
43
-
to set one at the docker prompt...
41
+
Root via localhost (docker exec) no longer requires a password according to [upstream behavior](https://mariadb.com/docs/server/security/user-account-management/authentication-from-mariadb-10-4), if you didn't set a root password for remote access during the initial start follow the instructions in the container log.
44
42
45
43
NOTE changing any of the MYSQL_ variables after the container has set up the initial databases has no effect, use the mysqladmin tool or cli to make changes.
46
44
@@ -85,10 +83,10 @@ app_setup_block: |
85
83
If user databases are not in a healthy state (sometimes caused by a failed upgrade), it may be remedied by running:
86
84
87
85
```shell
88
-
mariadb-check -u root -p<PASSWORD> -c -A # check all databases for errors
89
-
mariadb-check -u root -p<PASSWORD> -r -A # repair all databases
90
-
mariadb-check -u root -p<PASSWORD> -a -A # analyze all databases
91
-
mariadb-check -u root -p<PASSWORD> -o -A # optimize all databases
86
+
mariadb-check -c -A # check all databases for errors
87
+
mariadb-check -r -A # repair all databases
88
+
mariadb-check -a -A # analyze all databases
89
+
mariadb-check -o -A # optimize all databases
92
90
```
93
91
94
92
After running the above commands, you may need to run the upgrade command again.
@@ -98,7 +96,7 @@ app_setup_block: |
98
96
When this container initializes, if `MYSQL_ROOT_PASSWORD` is set an upgrade check will run. If an upgrade is required the log will indicate the need stop any services that are accessing databases in this container, and then run the command:
0 commit comments