2014-11-24 15:31:55 -08:00
#!/bin/bash
2016-01-26 09:22:48 -08:00
set -eo pipefail
2016-09-30 14:14:20 -07:00
shopt -s nullglob
2014-11-24 15:31:55 -08:00
2019-10-31 16:57:08 -07:00
# logging functions
mysql_log( ) {
local type = " $1 " ; shift
printf '%s [%s] [Entrypoint]: %s\n' " $( date --rfc-3339= seconds) " " $type " " $* "
}
mysql_note( ) {
mysql_log Note " $@ "
}
mysql_warn( ) {
mysql_log Warn " $@ " >& 2
}
mysql_error( ) {
mysql_log ERROR " $@ " >& 2
exit 1
}
2016-02-24 15:51:13 -08:00
2016-11-23 10:35:50 -08:00
# usage: file_env VAR [DEFAULT]
# ie: file_env 'XYZ_DB_PASSWORD' 'example'
# (will allow for "$XYZ_DB_PASSWORD_FILE" to fill in the value of
# "$XYZ_DB_PASSWORD" from a file, especially for Docker's secrets feature)
file_env( ) {
local var = " $1 "
local fileVar = " ${ var } _FILE "
local def = " ${ 2 :- } "
if [ " ${ !var :- } " ] && [ " ${ !fileVar :- } " ] ; then
2019-10-31 16:57:08 -07:00
mysql_error " Both $var and $fileVar are set (but are exclusive) "
2016-11-23 10:35:50 -08:00
fi
local val = " $def "
if [ " ${ !var :- } " ] ; then
val = " ${ !var } "
elif [ " ${ !fileVar :- } " ] ; then
val = " $( < " ${ !fileVar } " ) "
fi
export " $var " = " $val "
unset " $fileVar "
}
2020-11-11 15:50:00 -08:00
# set MARIADB_xyz from MYSQL_xyz when MARIADB_xyz is unset
# and make them the same value (so user scripts can use either)
_mariadb_file_env( ) {
local var = " $1 " ; shift
local maria = " MARIADB_ ${ var #MYSQL_ } "
file_env " $var " " $@ "
file_env " $maria " " ${ !var } "
if [ " ${ !maria :- } " ] ; then
export " $var " = " ${ !maria } "
fi
}
2019-10-31 16:57:08 -07:00
# check to see if this file is being run or sourced from another script
_is_sourced( ) {
# https://unix.stackexchange.com/a/215279
[ " ${# FUNCNAME [@] } " -ge 2 ] \
&& [ " ${ FUNCNAME [0] } " = '_is_sourced' ] \
&& [ " ${ FUNCNAME [1] } " = 'source' ]
}
# usage: docker_process_init_files [file [file [...]]]
# ie: docker_process_init_files /always-initdb.d/*
# process initializer files, based on file extensions
docker_process_init_files( ) {
# mysql here for backwards compatibility "${mysql[@]}"
2021-12-06 14:30:12 +11:00
# ShellCheck: mysql appears unused. Verify use (or export if used externally)
# shellcheck disable=SC2034
2019-10-31 16:57:08 -07:00
mysql = ( docker_process_sql )
2016-09-30 14:14:20 -07:00
2019-10-31 16:57:08 -07:00
echo
local f
for f; do
case " $f " in
2020-04-22 12:44:19 -07:00
*.sh)
# https://github.com/docker-library/postgres/issues/450#issuecomment-393167936
# https://github.com/docker-library/postgres/pull/452
if [ -x " $f " ] ; then
mysql_note " $0 : running $f "
" $f "
else
mysql_note " $0 : sourcing $f "
2021-12-06 14:30:12 +11:00
# ShellCheck can't follow non-constant source. Use a directive to specify location.
# shellcheck disable=SC1090
2020-04-22 12:44:19 -07:00
. " $f "
fi
; ;
2021-05-20 22:48:10 +02:00
*.sql) mysql_note " $0 : running $f " ; docker_process_sql < " $f " ; echo ; ;
*.sql.gz) mysql_note " $0 : running $f " ; gunzip -c " $f " | docker_process_sql; echo ; ;
*.sql.xz) mysql_note " $0 : running $f " ; xzcat " $f " | docker_process_sql; echo ; ;
*.sql.zst) mysql_note " $0 : running $f " ; zstd -dc " $f " | docker_process_sql; echo ; ;
*) mysql_warn " $0 : ignoring $f " ; ;
2019-10-31 16:57:08 -07:00
esac
echo
done
}
2016-09-30 14:14:20 -07:00
2024-06-20 18:00:53 +10:00
# arguments necessary to run "mariadbd --verbose --help" successfully (used for testing configuration validity and for extracting default/configured values)
2021-01-08 12:39:35 +01:00
_verboseHelpArgs = (
--verbose --help
)
2019-10-31 16:57:08 -07:00
mysql_check_config( ) {
2021-01-08 12:39:35 +01:00
local toRun = ( " $@ " " ${ _verboseHelpArgs [@] } " ) errors
2019-10-31 16:57:08 -07:00
if ! errors = " $( " ${ toRun [@] } " 2>& 1 >/dev/null) " ; then
2024-06-20 18:00:53 +10:00
mysql_error $'mariadbd failed while attempting to check config\n\tcommand was: ' " ${ toRun [*] } " $'\n\t' " $errors "
2016-09-30 14:14:20 -07:00
fi
}
2017-04-05 10:53:51 -07:00
# Fetch value from server config
2024-06-20 18:00:53 +10:00
# We use mariadbd --verbose --help instead of my_print_defaults because the
2017-04-05 10:53:51 -07:00
# latter only show values present in config files, and not server defaults
2019-10-31 16:57:08 -07:00
mysql_get_config( ) {
2017-04-05 10:53:51 -07:00
local conf = " $1 " ; shift
2021-01-08 12:39:35 +01:00
" $@ " " ${ _verboseHelpArgs [@] } " 2>/dev/null \
2019-10-31 16:57:08 -07:00
| awk -v conf = " $conf " '$1 == conf && /^[^ \t]/ { sub(/^[^ \t]+[ \t]+/, ""); print; exit }'
2018-11-12 14:37:58 -08:00
# match "datadir /some/path with/spaces in/it here" but not "--xyz=abc\n datadir (xyz)"
2016-05-17 12:48:56 -07:00
}
2021-03-16 13:15:36 +11:00
# Do a temporary startup of the MariaDB server, for init purposes
2019-10-31 16:57:08 -07:00
docker_temp_server_start( ) {
2022-03-17 09:44:04 +11:00
" $@ " --skip-networking --default-time-zone= SYSTEM --socket= " ${ SOCKET } " --wsrep_on= OFF \
2022-04-06 11:41:23 +10:00
--expire-logs-days= 0 \
2024-09-04 13:44:06 +10:00
--skip-slave-start \
2024-06-10 20:55:53 +10:00
--loose-innodb_buffer_pool_load_at_startup= 0 \
--skip-ssl --ssl-cert= '' --ssl-key= '' --ssl-ca= '' \
&
2022-02-21 13:41:02 +11:00
declare -g MARIADB_PID
MARIADB_PID = $!
2019-10-31 16:57:08 -07:00
mysql_note "Waiting for server startup"
2022-11-10 09:25:12 +01:00
# only use the root password if the database has already been initialized
2021-05-12 14:41:15 +10:00
# so that it won't try to fill in a password file when it hasn't been set yet
extraArgs = ( )
if [ -z " $DATABASE_ALREADY_EXISTS " ] ; then
extraArgs += ( '--dont-use-mysql-root-password' )
fi
2019-10-31 16:57:08 -07:00
local i
for i in { 30..0} ; do
2024-06-10 20:55:53 +10:00
if docker_process_sql " ${ extraArgs [@] } " --database= mysql \
--skip-ssl --skip-ssl-verify-server-cert \
<<< 'SELECT 1' & > /dev/null; then
2019-10-31 16:57:08 -07:00
break
fi
sleep 1
done
if [ " $i " = 0 ] ; then
mysql_error "Unable to start server."
fi
}
2024-06-20 18:00:53 +10:00
# Stop the server. When using a local socket file mariadb-admin will block until
2019-10-31 16:57:08 -07:00
# the shutdown is complete.
docker_temp_server_stop( ) {
2022-09-23 09:27:19 +10:00
kill " $MARIADB_PID "
wait " $MARIADB_PID "
2019-10-31 16:57:08 -07:00
}
# Verify that the minimally required password settings are set for new databases.
docker_verify_minimum_env( ) {
2023-10-06 13:33:40 +03:00
# Restoring from backup requires no environment variables
declare -g DATABASE_INIT_FROM_BACKUP
for file in /docker-entrypoint-initdb.d/*.tar{ .gz,.xz,.zst} ; do
if [ -f " ${ file } " ] ; then
DATABASE_INIT_FROM_BACKUP = 'true'
return
fi
done
2022-09-07 15:50:02 +02:00
if [ -z " $MARIADB_ROOT_PASSWORD " ] && [ -z " $MARIADB_ROOT_PASSWORD_HASH " ] && [ -z " $MARIADB_ALLOW_EMPTY_ROOT_PASSWORD " ] && [ -z " $MARIADB_RANDOM_ROOT_PASSWORD " ] ; then
mysql_error $'Database is uninitialized and password option is not specified\n\tYou need to specify one of MARIADB_ROOT_PASSWORD, MARIADB_ROOT_PASSWORD_HASH, MARIADB_ALLOW_EMPTY_ROOT_PASSWORD and MARIADB_RANDOM_ROOT_PASSWORD'
fi
# More preemptive exclusions of combinations should have been made before *PASSWORD_HASH was added, but for now we don't enforce due to compatibility.
if [ -n " $MARIADB_ROOT_PASSWORD " ] || [ -n " $MARIADB_ALLOW_EMPTY_ROOT_PASSWORD " ] || [ -n " $MARIADB_RANDOM_ROOT_PASSWORD " ] && [ -n " $MARIADB_ROOT_PASSWORD_HASH " ] ; then
mysql_error "Cannot specify MARIADB_ROOT_PASSWORD_HASH and another MARIADB_ROOT_PASSWORD* option."
fi
if [ -n " $MARIADB_PASSWORD " ] && [ -n " $MARIADB_PASSWORD_HASH " ] ; then
mysql_error "Cannot specify MARIADB_PASSWORD_HASH and MARIADB_PASSWORD option."
2019-10-31 16:57:08 -07:00
fi
MDEV-29762: Add capability for replication
These are controled by:
* MARIADB_MASTER_HOST - if specified, the master, and the container is a replica
* MARIADB_REPLICATION_PORT - port number
* MARIADB_REPLICATION_USER - create or use this user
* MARIADB_REPLICATION_PASSWORD - create or use this password
* MARIADB_REPLICATION_PASSWORD_HASH (on master only)
If MARIADB_MASTER_HOST isn't specified, the container is a master. In
this case, the MARIADB_REPLICATION_USER is created, with password{,hash},
and given the REPLICATION REPLICA grant, or REPLICATION SLAVE (for
10.3, 10.4).
If the MARIADB_MASTER_HOST is specified, CHANGE MASTER TO is used to
connect to the MARIADB_MASTER_HOST:MARIADB_MASTER_PORT(default 3306)
using the MARIADB_REPLICATION_USER. As the password is needed
MARIADB_REPLICATION_PASSWORD_HASH cannot be used on a replica.
CHANGE MASTER TO is executed with MASTER_CONNECT_RETRY=10 and the
replica is started by default.
The creation of the replication user is replicated along with the
master's /docker-entrypoint-initdb.d/ contents and MARIADB_DATABASE
/MARIADB_USER. The MARIADB_MYSQL_LOCALHOST_USER isn't replicated and
neither is the timezone data.
Signed-off-by: MdSahil-oss <Mohdssahil1@gmail.com>
Reviewed-by: Daniel Black <daniel@mariadb.org>
2023-04-01 01:02:21 +05:30
if [ -n " $MARIADB_REPLICATION_USER " ] ; then
if [ -z " $MARIADB_MASTER_HOST " ] ; then
# its a master, we're creating a user
if [ -z " $MARIADB_REPLICATION_PASSWORD " ] && [ -z " $MARIADB_REPLICATION_PASSWORD_HASH " ] ; then
mysql_error "MARIADB_REPLICATION_PASSWORD or MARIADB_REPLICATION_PASSWORD_HASH not found to create replication user for master"
fi
else
# its a replica
if [ -z " $MARIADB_REPLICATION_PASSWORD " ] ; then
mysql_error "MARIADB_REPLICATION_PASSWORD is mandatory to specify the replication on the replica image."
fi
if [ -n " $MARIADB_REPLICATION_PASSWORD_HASH " ] ; then
mysql_warn "MARIADB_REPLICATION_PASSWORD_HASH cannot be specified on a replica"
fi
fi
fi
if [ -n " $MARIADB_MASTER_HOST " ] && { [ -z " $MARIADB_REPLICATION_USER " ] || [ -z " $MARIADB_REPLICATION_PASSWORD " ] ; } ; then
mysql_error "For a replica, MARIADB_REPLICATION_USER and MARIADB_REPLICATION is mandatory."
fi
2019-10-31 16:57:08 -07:00
}
# creates folders for the database
# also ensures permission for user mysql of run as root
docker_create_db_directories( ) {
local user; user = " $( id -u) "
# TODO other directories that are used by default? like /var/lib/mysql-files
# see https://github.com/docker-library/mysql/issues/562
2016-05-17 12:48:56 -07:00
mkdir -p " $DATADIR "
2019-10-31 16:57:08 -07:00
if [ " $user " = "0" ] ; then
# this will cause less disk access than `chown -R`
2024-06-21 13:11:24 +10:00
find " $DATADIR " \! -user mysql \( -exec chown mysql: '{}' + -o -true \)
2021-04-09 13:47:28 +10:00
# See https://github.com/MariaDB/mariadb-docker/issues/363
2024-06-26 18:30:38 +10:00
if [ " ${ SOCKET : 0 : 1 } " != '@' ] ; then # not abstract sockets
find " ${ SOCKET %/* } " -maxdepth 0 \! -user mysql \( -exec chown mysql: '{}' \; -o -true \)
fi
2023-10-30 12:54:45 +11:00
# memory.pressure
local cgroup; cgroup = $( </proc/self/cgroup)
local mempressure = " /sys/fs/cgroup/ ${ cgroup : 3 } /memory.pressure "
if [ -w " $mempressure " ] ; then
chown mysql: " $mempressure " || mysql_warn " unable to change ownership of $mempressure , functionality unavailable to MariaDB "
else
mysql_warn " $mempressure not writable, functionality unavailable to MariaDB "
fi
2019-10-31 16:57:08 -07:00
fi
}
2015-08-11 16:39:56 -07:00
2021-11-19 17:31:42 +11:00
_mariadb_version( ) {
2024-05-20 09:36:24 +10:00
echo -n "%%MARIADB_VERSION_BASIC%%-MariaDB"
2021-11-19 17:31:42 +11:00
}
2019-10-31 16:57:08 -07:00
# initializes the database directory
docker_init_database_dir( ) {
mysql_note "Initializing database files"
2020-10-23 06:39:12 +11:00
installArgs = ( --datadir= " $DATADIR " --rpm --auth-root-authentication-method= normal )
2024-06-20 18:00:53 +10:00
# "Other options are passed to mariadbd." (so we pass all "mariadbd" arguments directly here)
2024-05-05 22:38:07 +02:00
local mariadbdArgs = ( )
for arg in " ${ @ : 2 } " ; do
# Check if the argument contains whitespace
2024-05-17 18:50:03 +10:00
if [ [ " $arg " = ~ [ [ :space:] ] ] ] ; then
mysql_warn " Not passing argument \' $arg \' to mariadb-install-db because mariadb-install-db does not support arguments with whitespace. "
2024-05-05 22:38:07 +02:00
else
2024-05-17 18:50:03 +10:00
mariadbdArgs += ( " $arg " )
2024-05-05 22:38:07 +02:00
fi
done
2024-06-20 18:00:53 +10:00
mariadb-install-db " ${ installArgs [@] } " " ${ mariadbdArgs [@] } " \
2024-08-30 17:18:57 +10:00
--cross-bootstrap \
2022-11-30 14:17:28 +11:00
--skip-test-db \
--old-mode= 'UTF8_IS_UTF8MB3' \
2022-04-06 11:41:23 +10:00
--default-time-zone= SYSTEM --enforce-storage-engine= \
--skip-log-bin \
--expire-logs-days= 0 \
2022-02-05 09:51:00 +11:00
--loose-innodb_buffer_pool_load_at_startup= 0 \
--loose-innodb_buffer_pool_dump_at_shutdown= 0
2019-10-31 16:57:08 -07:00
mysql_note "Database files initialized"
}
2015-08-11 16:39:56 -07:00
2019-10-31 16:57:08 -07:00
# Loads various settings that are used elsewhere in the script
# This should be called after mysql_check_config, but before any other functions
docker_setup_env( ) {
# Get config
Allow healthcheck@{127.0.0.1,::1,localhost} to exist to facilitate healthcheck --connect
healthcheck@{127.0.0.1,::1,localhost} users are granted USAGE by default, which
is enough for the non-replication healthchecks in healtcheck.sh.
The env variable MARIADB_HEALTHCHECK_GRANTS can replace USAGE with any
comma separated set of grants.
On initialization a generated password is created and saved in
$DATADIR/.my-healthcheck.cnf along with the server port and socket. If the
command args or default configuration file changes this may become out
of date. Because the password is generated in configuration file the
'#', comment, and '=' characters cannot be part of this password.
The healthcheck.cnf configuration file also sets protocol=tcp to
enforce indirectly that --connect being a standard part of the test. This is
required as starts of the service under --skip-networking should
never be considered healthy.
The healthcheck script also has the --defaults-extra-file set to this
.my-healthcheck.cnf file, if it exists (backwards compatible on
previously created datadirs), so that all new healthcheck invokations
use the authentication here by default.
The compatibility with old instances, without the .my-healthcheck.cnf is
preserved by non setting --defaults-extra-file.
The healthcheck --connect will increment the server status variable Aborted_connects
for each check, however now connection_error* counts are changed.
This also prevents any invalid password errors showing up in the
container log.
Closes #430
2023-05-16 10:12:28 +10:00
declare -g DATADIR SOCKET PORT
2019-10-31 16:57:08 -07:00
DATADIR = " $( mysql_get_config 'datadir' " $@ " ) "
SOCKET = " $( mysql_get_config 'socket' " $@ " ) "
Allow healthcheck@{127.0.0.1,::1,localhost} to exist to facilitate healthcheck --connect
healthcheck@{127.0.0.1,::1,localhost} users are granted USAGE by default, which
is enough for the non-replication healthchecks in healtcheck.sh.
The env variable MARIADB_HEALTHCHECK_GRANTS can replace USAGE with any
comma separated set of grants.
On initialization a generated password is created and saved in
$DATADIR/.my-healthcheck.cnf along with the server port and socket. If the
command args or default configuration file changes this may become out
of date. Because the password is generated in configuration file the
'#', comment, and '=' characters cannot be part of this password.
The healthcheck.cnf configuration file also sets protocol=tcp to
enforce indirectly that --connect being a standard part of the test. This is
required as starts of the service under --skip-networking should
never be considered healthy.
The healthcheck script also has the --defaults-extra-file set to this
.my-healthcheck.cnf file, if it exists (backwards compatible on
previously created datadirs), so that all new healthcheck invokations
use the authentication here by default.
The compatibility with old instances, without the .my-healthcheck.cnf is
preserved by non setting --defaults-extra-file.
The healthcheck --connect will increment the server status variable Aborted_connects
for each check, however now connection_error* counts are changed.
This also prevents any invalid password errors showing up in the
container log.
Closes #430
2023-05-16 10:12:28 +10:00
PORT = " $( mysql_get_config 'port' " $@ " ) "
2015-08-11 16:39:56 -07:00
2020-11-11 15:50:00 -08:00
2019-10-31 16:57:08 -07:00
# Initialize values that might be stored in a file
2020-11-11 15:50:00 -08:00
_mariadb_file_env 'MYSQL_ROOT_HOST' '%'
_mariadb_file_env 'MYSQL_DATABASE'
_mariadb_file_env 'MYSQL_USER'
_mariadb_file_env 'MYSQL_PASSWORD'
_mariadb_file_env 'MYSQL_ROOT_PASSWORD'
2022-09-07 15:50:02 +02:00
# No MYSQL_ compatibility needed for new variables
file_env 'MARIADB_PASSWORD_HASH'
file_env 'MARIADB_ROOT_PASSWORD_HASH'
MDEV-29762: Add capability for replication
These are controled by:
* MARIADB_MASTER_HOST - if specified, the master, and the container is a replica
* MARIADB_REPLICATION_PORT - port number
* MARIADB_REPLICATION_USER - create or use this user
* MARIADB_REPLICATION_PASSWORD - create or use this password
* MARIADB_REPLICATION_PASSWORD_HASH (on master only)
If MARIADB_MASTER_HOST isn't specified, the container is a master. In
this case, the MARIADB_REPLICATION_USER is created, with password{,hash},
and given the REPLICATION REPLICA grant, or REPLICATION SLAVE (for
10.3, 10.4).
If the MARIADB_MASTER_HOST is specified, CHANGE MASTER TO is used to
connect to the MARIADB_MASTER_HOST:MARIADB_MASTER_PORT(default 3306)
using the MARIADB_REPLICATION_USER. As the password is needed
MARIADB_REPLICATION_PASSWORD_HASH cannot be used on a replica.
CHANGE MASTER TO is executed with MASTER_CONNECT_RETRY=10 and the
replica is started by default.
The creation of the replication user is replicated along with the
master's /docker-entrypoint-initdb.d/ contents and MARIADB_DATABASE
/MARIADB_USER. The MARIADB_MYSQL_LOCALHOST_USER isn't replicated and
neither is the timezone data.
Signed-off-by: MdSahil-oss <Mohdssahil1@gmail.com>
Reviewed-by: Daniel Black <daniel@mariadb.org>
2023-04-01 01:02:21 +05:30
# env variables related to replication
file_env 'MARIADB_REPLICATION_USER'
file_env 'MARIADB_REPLICATION_PASSWORD'
file_env 'MARIADB_REPLICATION_PASSWORD_HASH'
# env variables related to master
file_env 'MARIADB_MASTER_HOST'
file_env 'MARIADB_MASTER_PORT' 3306
2020-11-11 15:50:00 -08:00
# set MARIADB_ from MYSQL_ when it is unset and then make them the same value
2021-03-01 16:59:43 +11:00
: " ${ MARIADB_ALLOW_EMPTY_ROOT_PASSWORD : = ${ MYSQL_ALLOW_EMPTY_PASSWORD :- } } "
export MYSQL_ALLOW_EMPTY_PASSWORD = " $MARIADB_ALLOW_EMPTY_ROOT_PASSWORD " MARIADB_ALLOW_EMPTY_ROOT_PASSWORD
2020-11-11 15:50:00 -08:00
: " ${ MARIADB_RANDOM_ROOT_PASSWORD : = ${ MYSQL_RANDOM_ROOT_PASSWORD :- } } "
export MYSQL_RANDOM_ROOT_PASSWORD = " $MARIADB_RANDOM_ROOT_PASSWORD " MARIADB_RANDOM_ROOT_PASSWORD
2021-03-01 14:52:58 +11:00
: " ${ MARIADB_INITDB_SKIP_TZINFO : = ${ MYSQL_INITDB_SKIP_TZINFO :- } } "
export MYSQL_INITDB_SKIP_TZINFO = " $MARIADB_INITDB_SKIP_TZINFO " MARIADB_INITDB_SKIP_TZINFO
2015-08-11 16:39:56 -07:00
2019-10-31 16:57:08 -07:00
declare -g DATABASE_ALREADY_EXISTS
if [ -d " $DATADIR /mysql " ] ; then
DATABASE_ALREADY_EXISTS = 'true'
fi
}
2017-04-05 10:53:51 -07:00
2021-05-12 14:41:15 +10:00
# Execute the client, use via docker_process_sql to handle root password
docker_exec_client( ) {
# args sent in can override this db, since they will be later in the command
if [ -n " $MYSQL_DATABASE " ] ; then
set -- --database= " $MYSQL_DATABASE " " $@ "
fi
2024-06-20 18:00:53 +10:00
mariadb --protocol= socket -uroot -hlocalhost --socket= " ${ SOCKET } " " $@ "
2021-05-12 14:41:15 +10:00
}
2019-10-31 16:57:08 -07:00
# Execute sql script, passed via stdin
# usage: docker_process_sql [--dont-use-mysql-root-password] [mysql-cli-args]
# ie: docker_process_sql --database=mydb <<<'INSERT ...'
# ie: docker_process_sql --dont-use-mysql-root-password --database=mydb <my-file.sql
docker_process_sql( ) {
if [ '--dont-use-mysql-root-password' = " $1 " ] ; then
shift
2021-12-06 14:30:12 +11:00
MYSQL_PWD = '' docker_exec_client " $@ "
2021-03-12 15:28:01 +11:00
else
2021-05-12 14:41:15 +10:00
MYSQL_PWD = $MARIADB_ROOT_PASSWORD docker_exec_client " $@ "
2019-10-31 16:57:08 -07:00
fi
2021-03-12 15:28:01 +11:00
}
# SQL escape the string $1 to be placed in a string literal.
# escape, \ followed by '
docker_sql_escape_string_literal( ) {
2021-07-13 10:05:14 +10:00
local newline = $'\n'
2021-07-13 09:42:01 +10:00
local escaped = ${ 1 // \\ / \\ \\ }
2021-07-13 10:05:14 +10:00
escaped = " ${ escaped // $newline / \\ n } "
2021-07-13 09:42:01 +10:00
echo " ${ escaped // \' / \\ \' } "
2019-10-31 16:57:08 -07:00
}
2017-04-05 10:53:51 -07:00
MDEV-29762: Add capability for replication
These are controled by:
* MARIADB_MASTER_HOST - if specified, the master, and the container is a replica
* MARIADB_REPLICATION_PORT - port number
* MARIADB_REPLICATION_USER - create or use this user
* MARIADB_REPLICATION_PASSWORD - create or use this password
* MARIADB_REPLICATION_PASSWORD_HASH (on master only)
If MARIADB_MASTER_HOST isn't specified, the container is a master. In
this case, the MARIADB_REPLICATION_USER is created, with password{,hash},
and given the REPLICATION REPLICA grant, or REPLICATION SLAVE (for
10.3, 10.4).
If the MARIADB_MASTER_HOST is specified, CHANGE MASTER TO is used to
connect to the MARIADB_MASTER_HOST:MARIADB_MASTER_PORT(default 3306)
using the MARIADB_REPLICATION_USER. As the password is needed
MARIADB_REPLICATION_PASSWORD_HASH cannot be used on a replica.
CHANGE MASTER TO is executed with MASTER_CONNECT_RETRY=10 and the
replica is started by default.
The creation of the replication user is replicated along with the
master's /docker-entrypoint-initdb.d/ contents and MARIADB_DATABASE
/MARIADB_USER. The MARIADB_MYSQL_LOCALHOST_USER isn't replicated and
neither is the timezone data.
Signed-off-by: MdSahil-oss <Mohdssahil1@gmail.com>
Reviewed-by: Daniel Black <daniel@mariadb.org>
2023-04-01 01:02:21 +05:30
# Creates replication user
create_replica_user( ) {
if [ -n " $MARIADB_REPLICATION_PASSWORD_HASH " ] ; then
echo " CREATE USER ' $MARIADB_REPLICATION_USER '@'%' IDENTIFIED BY PASSWORD ' $MARIADB_REPLICATION_PASSWORD_HASH '; "
else
# SQL escape the user password, \ followed by '
local userPasswordEscaped
2024-01-30 22:21:08 +11:00
userPasswordEscaped = $( docker_sql_escape_string_literal " ${ MARIADB_REPLICATION_PASSWORD } " )
MDEV-29762: Add capability for replication
These are controled by:
* MARIADB_MASTER_HOST - if specified, the master, and the container is a replica
* MARIADB_REPLICATION_PORT - port number
* MARIADB_REPLICATION_USER - create or use this user
* MARIADB_REPLICATION_PASSWORD - create or use this password
* MARIADB_REPLICATION_PASSWORD_HASH (on master only)
If MARIADB_MASTER_HOST isn't specified, the container is a master. In
this case, the MARIADB_REPLICATION_USER is created, with password{,hash},
and given the REPLICATION REPLICA grant, or REPLICATION SLAVE (for
10.3, 10.4).
If the MARIADB_MASTER_HOST is specified, CHANGE MASTER TO is used to
connect to the MARIADB_MASTER_HOST:MARIADB_MASTER_PORT(default 3306)
using the MARIADB_REPLICATION_USER. As the password is needed
MARIADB_REPLICATION_PASSWORD_HASH cannot be used on a replica.
CHANGE MASTER TO is executed with MASTER_CONNECT_RETRY=10 and the
replica is started by default.
The creation of the replication user is replicated along with the
master's /docker-entrypoint-initdb.d/ contents and MARIADB_DATABASE
/MARIADB_USER. The MARIADB_MYSQL_LOCALHOST_USER isn't replicated and
neither is the timezone data.
Signed-off-by: MdSahil-oss <Mohdssahil1@gmail.com>
Reviewed-by: Daniel Black <daniel@mariadb.org>
2023-04-01 01:02:21 +05:30
echo " CREATE USER ' $MARIADB_REPLICATION_USER '@'%' IDENTIFIED BY ' $userPasswordEscaped '; "
fi
echo " GRANT REPLICATION REPLICA ON *.* TO ' $MARIADB_REPLICATION_USER '@'%'; "
}
2024-01-24 15:03:55 +11:00
# Create healthcheck users
create_healthcheck_users( ) {
local healthCheckGrant = USAGE
local healthCheckConnectPass
local healthCheckConnectPassEscaped
healthCheckConnectPass = " $( pwgen --numerals --capitalize --symbols --remove-chars= "=#'\\" -1 32) "
2024-01-30 22:21:08 +11:00
healthCheckConnectPassEscaped = $( docker_sql_escape_string_literal " ${ healthCheckConnectPass } " )
2024-01-24 15:03:55 +11:00
if [ -n " $MARIADB_HEALTHCHECK_GRANTS " ] ; then
healthCheckGrant = " $MARIADB_HEALTHCHECK_GRANTS "
fi
for host in 127.0.0.1 ::1 localhost; do
echo " CREATE USER IF NOT EXISTS healthcheck@' $host ' IDENTIFIED BY ' $healthCheckConnectPassEscaped '; "
# doing this so if the users exists, we're just setting the password, and not replacing the existing grants
echo " SET PASSWORD FOR healthcheck@' $host ' = PASSWORD(' $healthCheckConnectPassEscaped '); "
echo " GRANT $healthCheckGrant ON *.* TO healthcheck@' $host '; "
done
local maskPreserve
maskPreserve = $( umask -p)
umask 0077
2024-06-25 15:30:16 +10:00
echo -e " [mariadb-client]\\nport= $PORT \\nsocket= $SOCKET \\nuser=healthcheck\\npassword= $healthCheckConnectPass \\n " > " $DATADIR " /.my-healthcheck.cnf
2024-01-24 15:03:55 +11:00
$maskPreserve
}
2019-10-31 16:57:08 -07:00
# Initializes database with timezone info and root password, plus optional extra db/user
docker_setup_db( ) {
# Load timezone info into database
2021-03-01 14:52:58 +11:00
if [ -z " $MARIADB_INITDB_SKIP_TZINFO " ] ; then
2022-05-12 15:27:48 +10:00
# --skip-write-binlog usefully disables binary logging
# but also outputs LOCK TABLES to improve the IO of
# Aria (MDEV-23326) for 10.4+.
2024-06-20 18:00:53 +10:00
mariadb-tzinfo-to-sql --skip-write-binlog /usr/share/zoneinfo \
2022-10-17 14:37:52 +11:00
| docker_process_sql --dont-use-mysql-root-password --database= mysql
2020-08-11 10:04:03 +10:00
# tell docker_process_sql to not use MYSQL_ROOT_PASSWORD since it is not set yet
2019-10-31 16:57:08 -07:00
fi
# Generate random root password
2021-03-01 14:52:58 +11:00
if [ -n " $MARIADB_RANDOM_ROOT_PASSWORD " ] ; then
2021-04-29 11:29:35 +10:00
MARIADB_ROOT_PASSWORD = " $( pwgen --numerals --capitalize --symbols --remove-chars= "'\\" -1 32) "
export MARIADB_ROOT_PASSWORD MYSQL_ROOT_PASSWORD = $MARIADB_ROOT_PASSWORD
2021-03-01 14:52:58 +11:00
mysql_note " GENERATED ROOT PASSWORD: $MARIADB_ROOT_PASSWORD "
2019-10-31 16:57:08 -07:00
fi
2022-09-07 15:50:02 +02:00
# Creates root users for non-localhost hosts
2019-10-31 16:57:08 -07:00
local rootCreate =
2022-09-22 08:43:18 +10:00
local rootPasswordEscaped =
if [ -n " $MARIADB_ROOT_PASSWORD " ] ; then
# Sets root password and creates root users for non-localhost hosts
2024-01-30 22:21:08 +11:00
rootPasswordEscaped = $( docker_sql_escape_string_literal " ${ MARIADB_ROOT_PASSWORD } " )
2022-09-22 08:43:18 +10:00
fi
2021-03-12 15:28:01 +11:00
2019-10-31 16:57:08 -07:00
# default root to listen for connections from anywhere
2021-03-01 14:52:58 +11:00
if [ -n " $MARIADB_ROOT_HOST " ] && [ " $MARIADB_ROOT_HOST " != 'localhost' ] ; then
2022-09-23 09:27:19 +10:00
# ref "read -d ''", no, we don't care if read finds a terminating character in this heredoc
# https://unix.stackexchange.com/questions/265149/why-is-set-o-errexit-breaking-this-read-heredoc-expression/265151#265151
if [ -n " $MARIADB_ROOT_PASSWORD_HASH " ] ; then
2022-09-07 15:50:02 +02:00
read -r -d '' rootCreate <<-EOSQL || true
2022-09-23 09:27:19 +10:00
CREATE USER 'root' @'${MARIADB_ROOT_HOST}' IDENTIFIED BY PASSWORD '${MARIADB_ROOT_PASSWORD_HASH}' ;
2022-09-07 15:50:02 +02:00
GRANT ALL ON *.* TO 'root' @'${MARIADB_ROOT_HOST}' WITH GRANT OPTION ;
2023-09-20 14:26:32 +10:00
GRANT PROXY ON '' @'%' TO 'root' @'${MARIADB_ROOT_HOST}' WITH GRANT OPTION;
2022-09-07 15:50:02 +02:00
EOSQL
else
read -r -d '' rootCreate <<-EOSQL || true
2022-09-23 09:27:19 +10:00
CREATE USER 'root' @'${MARIADB_ROOT_HOST}' IDENTIFIED BY '${rootPasswordEscaped}' ;
2022-09-07 15:50:02 +02:00
GRANT ALL ON *.* TO 'root' @'${MARIADB_ROOT_HOST}' WITH GRANT OPTION ;
2023-09-20 14:26:32 +10:00
GRANT PROXY ON '' @'%' TO 'root' @'${MARIADB_ROOT_HOST}' WITH GRANT OPTION;
2022-09-07 15:50:02 +02:00
EOSQL
fi
2019-10-31 16:57:08 -07:00
fi
2015-08-26 11:13:23 -07:00
MDEV-27732: Add env MARIADB_MYSQL_LOCALHOST_{USER,GRANTS}
We create a mysql@localhost user under MARIADB_MYSQL_LOCALHOST_USER=1
with its default USAGE privileges.
This gives access to SHOW GLOBAL STATUS/VARIABLES but no other
real access including database visibility or process visibility.
Being a @localhost this restricts access to via the unix socket.
The level of access can be increased controlled by the environment variable
MARIADB_MYSQL_LOCALHOST_GRANTS.
If you are using monitoring replication or processes addition
privileges are required, and the setting of the environment variable
is the comma separated list of grants possible. For the moment,
these are a set of global grants only.
If you share the unix socket location, /var/run/mysqld by default,
as a volume with another container, you have effectively given that
container the mysql@localhost provided they have the same uid map
or can create arbitrary users.
This can be good for things like backup. This would require the
datadir volume as well and the set of privileges
(https://mariadb.com/kb/en/mariabackup-overview/#authentication-and-privileges).
Any grants of UPDATE on mysql database will mean that the
mysql@localhost user can manipulate any other user, potentially
transparently adding unix_socket auth (in 10.4+), and the being able
to gain their privileges.
Grants of CREATE USER, or INSERT on the mysql database allow the
creation of user and privilege escalation.
For these reasons, ALL for MARIADB_MYSQL_LOCALHOST_GRANTS gains a
warning.
Many thanks to Daniel Rudolf for all the reviews and the support
to develop this feature.
2022-02-01 17:50:49 +11:00
local mysqlAtLocalhost =
local mysqlAtLocalhostGrants =
# Install mysql@localhost user
2022-02-14 14:58:08 +11:00
if [ -n " $MARIADB_MYSQL_LOCALHOST_USER " ] ; then
MDEV-27732: Add env MARIADB_MYSQL_LOCALHOST_{USER,GRANTS}
We create a mysql@localhost user under MARIADB_MYSQL_LOCALHOST_USER=1
with its default USAGE privileges.
This gives access to SHOW GLOBAL STATUS/VARIABLES but no other
real access including database visibility or process visibility.
Being a @localhost this restricts access to via the unix socket.
The level of access can be increased controlled by the environment variable
MARIADB_MYSQL_LOCALHOST_GRANTS.
If you are using monitoring replication or processes addition
privileges are required, and the setting of the environment variable
is the comma separated list of grants possible. For the moment,
these are a set of global grants only.
If you share the unix socket location, /var/run/mysqld by default,
as a volume with another container, you have effectively given that
container the mysql@localhost provided they have the same uid map
or can create arbitrary users.
This can be good for things like backup. This would require the
datadir volume as well and the set of privileges
(https://mariadb.com/kb/en/mariabackup-overview/#authentication-and-privileges).
Any grants of UPDATE on mysql database will mean that the
mysql@localhost user can manipulate any other user, potentially
transparently adding unix_socket auth (in 10.4+), and the being able
to gain their privileges.
Grants of CREATE USER, or INSERT on the mysql database allow the
creation of user and privilege escalation.
For these reasons, ALL for MARIADB_MYSQL_LOCALHOST_GRANTS gains a
warning.
Many thanks to Daniel Rudolf for all the reviews and the support
to develop this feature.
2022-02-01 17:50:49 +11:00
read -r -d '' mysqlAtLocalhost <<-EOSQL || true
2023-05-11 12:11:51 +10:00
CREATE USER mysql@localhost IDENTIFIED VIA unix_socket;
MDEV-27732: Add env MARIADB_MYSQL_LOCALHOST_{USER,GRANTS}
We create a mysql@localhost user under MARIADB_MYSQL_LOCALHOST_USER=1
with its default USAGE privileges.
This gives access to SHOW GLOBAL STATUS/VARIABLES but no other
real access including database visibility or process visibility.
Being a @localhost this restricts access to via the unix socket.
The level of access can be increased controlled by the environment variable
MARIADB_MYSQL_LOCALHOST_GRANTS.
If you are using monitoring replication or processes addition
privileges are required, and the setting of the environment variable
is the comma separated list of grants possible. For the moment,
these are a set of global grants only.
If you share the unix socket location, /var/run/mysqld by default,
as a volume with another container, you have effectively given that
container the mysql@localhost provided they have the same uid map
or can create arbitrary users.
This can be good for things like backup. This would require the
datadir volume as well and the set of privileges
(https://mariadb.com/kb/en/mariabackup-overview/#authentication-and-privileges).
Any grants of UPDATE on mysql database will mean that the
mysql@localhost user can manipulate any other user, potentially
transparently adding unix_socket auth (in 10.4+), and the being able
to gain their privileges.
Grants of CREATE USER, or INSERT on the mysql database allow the
creation of user and privilege escalation.
For these reasons, ALL for MARIADB_MYSQL_LOCALHOST_GRANTS gains a
warning.
Many thanks to Daniel Rudolf for all the reviews and the support
to develop this feature.
2022-02-01 17:50:49 +11:00
EOSQL
if [ -n " $MARIADB_MYSQL_LOCALHOST_GRANTS " ] ; then
2022-02-10 17:45:49 +11:00
if [ " $MARIADB_MYSQL_LOCALHOST_GRANTS " != USAGE ] ; then
mysql_warn "Excessive privileges ON *.* TO mysql@localhost facilitates risks to the confidentiality, integrity and availability of data stored"
MDEV-27732: Add env MARIADB_MYSQL_LOCALHOST_{USER,GRANTS}
We create a mysql@localhost user under MARIADB_MYSQL_LOCALHOST_USER=1
with its default USAGE privileges.
This gives access to SHOW GLOBAL STATUS/VARIABLES but no other
real access including database visibility or process visibility.
Being a @localhost this restricts access to via the unix socket.
The level of access can be increased controlled by the environment variable
MARIADB_MYSQL_LOCALHOST_GRANTS.
If you are using monitoring replication or processes addition
privileges are required, and the setting of the environment variable
is the comma separated list of grants possible. For the moment,
these are a set of global grants only.
If you share the unix socket location, /var/run/mysqld by default,
as a volume with another container, you have effectively given that
container the mysql@localhost provided they have the same uid map
or can create arbitrary users.
This can be good for things like backup. This would require the
datadir volume as well and the set of privileges
(https://mariadb.com/kb/en/mariabackup-overview/#authentication-and-privileges).
Any grants of UPDATE on mysql database will mean that the
mysql@localhost user can manipulate any other user, potentially
transparently adding unix_socket auth (in 10.4+), and the being able
to gain their privileges.
Grants of CREATE USER, or INSERT on the mysql database allow the
creation of user and privilege escalation.
For these reasons, ALL for MARIADB_MYSQL_LOCALHOST_GRANTS gains a
warning.
Many thanks to Daniel Rudolf for all the reviews and the support
to develop this feature.
2022-02-01 17:50:49 +11:00
fi
mysqlAtLocalhostGrants = " GRANT ${ MARIADB_MYSQL_LOCALHOST_GRANTS } ON *.* TO mysql@localhost; " ;
fi
fi
2024-01-24 15:03:55 +11:00
local createHealthCheckUsers
createHealthCheckUsers = $( create_healthcheck_users)
Allow healthcheck@{127.0.0.1,::1,localhost} to exist to facilitate healthcheck --connect
healthcheck@{127.0.0.1,::1,localhost} users are granted USAGE by default, which
is enough for the non-replication healthchecks in healtcheck.sh.
The env variable MARIADB_HEALTHCHECK_GRANTS can replace USAGE with any
comma separated set of grants.
On initialization a generated password is created and saved in
$DATADIR/.my-healthcheck.cnf along with the server port and socket. If the
command args or default configuration file changes this may become out
of date. Because the password is generated in configuration file the
'#', comment, and '=' characters cannot be part of this password.
The healthcheck.cnf configuration file also sets protocol=tcp to
enforce indirectly that --connect being a standard part of the test. This is
required as starts of the service under --skip-networking should
never be considered healthy.
The healthcheck script also has the --defaults-extra-file set to this
.my-healthcheck.cnf file, if it exists (backwards compatible on
previously created datadirs), so that all new healthcheck invokations
use the authentication here by default.
The compatibility with old instances, without the .my-healthcheck.cnf is
preserved by non setting --defaults-extra-file.
The healthcheck --connect will increment the server status variable Aborted_connects
for each check, however now connection_error* counts are changed.
This also prevents any invalid password errors showing up in the
container log.
Closes #430
2023-05-16 10:12:28 +10:00
2022-09-23 12:31:48 +10:00
local rootLocalhostPass =
if [ -z " $MARIADB_ROOT_PASSWORD_HASH " ] ; then
# handle MARIADB_ROOT_PASSWORD_HASH for root@localhost after /docker-entrypoint-initdb.d
rootLocalhostPass = " SET PASSWORD FOR 'root'@'localhost'= PASSWORD(' ${ rootPasswordEscaped } '); "
2022-09-23 09:27:19 +10:00
fi
2015-08-11 16:39:56 -07:00
2022-09-23 09:27:19 +10:00
local createDatabase =
2019-10-31 16:57:08 -07:00
# Creates a custom database and user if specified
2021-03-01 14:52:58 +11:00
if [ -n " $MARIADB_DATABASE " ] ; then
mysql_note " Creating database ${ MARIADB_DATABASE } "
2022-09-23 09:27:19 +10:00
createDatabase = " CREATE DATABASE IF NOT EXISTS \` $MARIADB_DATABASE \`; "
2019-10-31 16:57:08 -07:00
fi
2015-08-11 16:39:56 -07:00
2022-09-23 09:27:19 +10:00
local createUser =
local userGrants =
2022-09-07 15:50:02 +02:00
if [ -n " $MARIADB_PASSWORD " ] || [ -n " $MARIADB_PASSWORD_HASH " ] && [ -n " $MARIADB_USER " ] ; then
2021-03-01 14:52:58 +11:00
mysql_note " Creating user ${ MARIADB_USER } "
2022-09-23 09:27:19 +10:00
if [ -n " $MARIADB_PASSWORD_HASH " ] ; then
createUser = " CREATE USER ' $MARIADB_USER '@'%' IDENTIFIED BY PASSWORD ' $MARIADB_PASSWORD_HASH '; "
else
2022-09-07 15:50:02 +02:00
# SQL escape the user password, \ followed by '
local userPasswordEscaped
2024-01-30 22:21:08 +11:00
userPasswordEscaped = $( docker_sql_escape_string_literal " ${ MARIADB_PASSWORD } " )
2022-09-23 09:27:19 +10:00
createUser = " CREATE USER ' $MARIADB_USER '@'%' IDENTIFIED BY ' $userPasswordEscaped '; "
2022-09-07 15:50:02 +02:00
fi
2019-10-31 16:57:08 -07:00
2021-03-01 14:52:58 +11:00
if [ -n " $MARIADB_DATABASE " ] ; then
mysql_note " Giving user ${ MARIADB_USER } access to schema ${ MARIADB_DATABASE } "
2022-09-23 09:27:19 +10:00
userGrants = " GRANT ALL ON \` ${ MARIADB_DATABASE //_/ \\ _ } \`.* TO ' $MARIADB_USER '@'%'; "
2014-11-24 15:31:55 -08:00
fi
2019-10-31 16:57:08 -07:00
fi
2022-09-23 09:27:19 +10:00
MDEV-29762: Add capability for replication
These are controled by:
* MARIADB_MASTER_HOST - if specified, the master, and the container is a replica
* MARIADB_REPLICATION_PORT - port number
* MARIADB_REPLICATION_USER - create or use this user
* MARIADB_REPLICATION_PASSWORD - create or use this password
* MARIADB_REPLICATION_PASSWORD_HASH (on master only)
If MARIADB_MASTER_HOST isn't specified, the container is a master. In
this case, the MARIADB_REPLICATION_USER is created, with password{,hash},
and given the REPLICATION REPLICA grant, or REPLICATION SLAVE (for
10.3, 10.4).
If the MARIADB_MASTER_HOST is specified, CHANGE MASTER TO is used to
connect to the MARIADB_MASTER_HOST:MARIADB_MASTER_PORT(default 3306)
using the MARIADB_REPLICATION_USER. As the password is needed
MARIADB_REPLICATION_PASSWORD_HASH cannot be used on a replica.
CHANGE MASTER TO is executed with MASTER_CONNECT_RETRY=10 and the
replica is started by default.
The creation of the replication user is replicated along with the
master's /docker-entrypoint-initdb.d/ contents and MARIADB_DATABASE
/MARIADB_USER. The MARIADB_MYSQL_LOCALHOST_USER isn't replicated and
neither is the timezone data.
Signed-off-by: MdSahil-oss <Mohdssahil1@gmail.com>
Reviewed-by: Daniel Black <daniel@mariadb.org>
2023-04-01 01:02:21 +05:30
# To create replica user
local createReplicaUser =
local changeMasterTo =
if [ -n " $MARIADB_REPLICATION_USER " ] ; then
if [ -z " $MARIADB_MASTER_HOST " ] ; then
# on master
mysql_note " Creating user ${ MARIADB_REPLICATION_USER } "
createReplicaUser = $( create_replica_user)
else
# on replica
local rplPasswordEscaped
2024-01-30 22:21:08 +11:00
rplPasswordEscaped = $( docker_sql_escape_string_literal " ${ MARIADB_REPLICATION_PASSWORD } " )
2023-05-11 11:01:03 +10:00
# SC cannot follow how MARIADB_MASTER_PORT is assigned a default value.
# shellcheck disable=SC2153
MDEV-29762: Add capability for replication
These are controled by:
* MARIADB_MASTER_HOST - if specified, the master, and the container is a replica
* MARIADB_REPLICATION_PORT - port number
* MARIADB_REPLICATION_USER - create or use this user
* MARIADB_REPLICATION_PASSWORD - create or use this password
* MARIADB_REPLICATION_PASSWORD_HASH (on master only)
If MARIADB_MASTER_HOST isn't specified, the container is a master. In
this case, the MARIADB_REPLICATION_USER is created, with password{,hash},
and given the REPLICATION REPLICA grant, or REPLICATION SLAVE (for
10.3, 10.4).
If the MARIADB_MASTER_HOST is specified, CHANGE MASTER TO is used to
connect to the MARIADB_MASTER_HOST:MARIADB_MASTER_PORT(default 3306)
using the MARIADB_REPLICATION_USER. As the password is needed
MARIADB_REPLICATION_PASSWORD_HASH cannot be used on a replica.
CHANGE MASTER TO is executed with MASTER_CONNECT_RETRY=10 and the
replica is started by default.
The creation of the replication user is replicated along with the
master's /docker-entrypoint-initdb.d/ contents and MARIADB_DATABASE
/MARIADB_USER. The MARIADB_MYSQL_LOCALHOST_USER isn't replicated and
neither is the timezone data.
Signed-off-by: MdSahil-oss <Mohdssahil1@gmail.com>
Reviewed-by: Daniel Black <daniel@mariadb.org>
2023-04-01 01:02:21 +05:30
changeMasterTo = " CHANGE MASTER TO MASTER_HOST=' $MARIADB_MASTER_HOST ', MASTER_USER=' $MARIADB_REPLICATION_USER ', MASTER_PASSWORD=' $rplPasswordEscaped ', MASTER_PORT= $MARIADB_MASTER_PORT , MASTER_CONNECT_RETRY=10; "
fi
fi
2022-09-23 09:27:19 +10:00
mysql_note "Securing system users (equivalent to running mysql_secure_installation)"
# tell docker_process_sql to not use MARIADB_ROOT_PASSWORD since it is just now being set
# --binary-mode to save us from the semi-mad users go out of their way to confuse the encoding.
docker_process_sql --dont-use-mysql-root-password --database= mysql --binary-mode <<-EOSQL
-- Securing system users shouldn' t be replicated
SET @orig_sql_log_bin= @@SESSION.SQL_LOG_BIN;
SET @@SESSION.SQL_LOG_BIN= 0;
-- we need the SQL_MODE NO_BACKSLASH_ESCAPES mode to be clear for the password to be set
SET @@SESSION.SQL_MODE= REPLACE( @@SESSION.SQL_MODE, 'NO_BACKSLASH_ESCAPES' , '' ) ;
DROP USER IF EXISTS root@'127.0.0.1' , root@'::1' ;
EXECUTE IMMEDIATE CONCAT( 'DROP USER IF EXISTS root@\' ', @@hostname,' \' ' ) ;
2022-09-23 12:31:48 +10:00
${ rootLocalhostPass }
2022-09-23 09:27:19 +10:00
${ rootCreate }
${ mysqlAtLocalhost }
${ mysqlAtLocalhostGrants }
2024-01-24 15:03:55 +11:00
${ createHealthCheckUsers }
2022-09-23 09:27:19 +10:00
-- end of securing system users, rest of init now...
SET @@SESSION.SQL_LOG_BIN= @orig_sql_log_bin;
-- create users/databases
${ createDatabase }
${ createUser }
MDEV-29762: Add capability for replication
These are controled by:
* MARIADB_MASTER_HOST - if specified, the master, and the container is a replica
* MARIADB_REPLICATION_PORT - port number
* MARIADB_REPLICATION_USER - create or use this user
* MARIADB_REPLICATION_PASSWORD - create or use this password
* MARIADB_REPLICATION_PASSWORD_HASH (on master only)
If MARIADB_MASTER_HOST isn't specified, the container is a master. In
this case, the MARIADB_REPLICATION_USER is created, with password{,hash},
and given the REPLICATION REPLICA grant, or REPLICATION SLAVE (for
10.3, 10.4).
If the MARIADB_MASTER_HOST is specified, CHANGE MASTER TO is used to
connect to the MARIADB_MASTER_HOST:MARIADB_MASTER_PORT(default 3306)
using the MARIADB_REPLICATION_USER. As the password is needed
MARIADB_REPLICATION_PASSWORD_HASH cannot be used on a replica.
CHANGE MASTER TO is executed with MASTER_CONNECT_RETRY=10 and the
replica is started by default.
The creation of the replication user is replicated along with the
master's /docker-entrypoint-initdb.d/ contents and MARIADB_DATABASE
/MARIADB_USER. The MARIADB_MYSQL_LOCALHOST_USER isn't replicated and
neither is the timezone data.
Signed-off-by: MdSahil-oss <Mohdssahil1@gmail.com>
Reviewed-by: Daniel Black <daniel@mariadb.org>
2023-04-01 01:02:21 +05:30
${ createReplicaUser }
2022-09-23 09:27:19 +10:00
${ userGrants }
MDEV-29762: Add capability for replication
These are controled by:
* MARIADB_MASTER_HOST - if specified, the master, and the container is a replica
* MARIADB_REPLICATION_PORT - port number
* MARIADB_REPLICATION_USER - create or use this user
* MARIADB_REPLICATION_PASSWORD - create or use this password
* MARIADB_REPLICATION_PASSWORD_HASH (on master only)
If MARIADB_MASTER_HOST isn't specified, the container is a master. In
this case, the MARIADB_REPLICATION_USER is created, with password{,hash},
and given the REPLICATION REPLICA grant, or REPLICATION SLAVE (for
10.3, 10.4).
If the MARIADB_MASTER_HOST is specified, CHANGE MASTER TO is used to
connect to the MARIADB_MASTER_HOST:MARIADB_MASTER_PORT(default 3306)
using the MARIADB_REPLICATION_USER. As the password is needed
MARIADB_REPLICATION_PASSWORD_HASH cannot be used on a replica.
CHANGE MASTER TO is executed with MASTER_CONNECT_RETRY=10 and the
replica is started by default.
The creation of the replication user is replicated along with the
master's /docker-entrypoint-initdb.d/ contents and MARIADB_DATABASE
/MARIADB_USER. The MARIADB_MYSQL_LOCALHOST_USER isn't replicated and
neither is the timezone data.
Signed-off-by: MdSahil-oss <Mohdssahil1@gmail.com>
Reviewed-by: Daniel Black <daniel@mariadb.org>
2023-04-01 01:02:21 +05:30
${ changeMasterTo }
2022-09-23 09:27:19 +10:00
EOSQL
2019-10-31 16:57:08 -07:00
}
2015-08-11 16:39:56 -07:00
2023-10-05 23:16:04 +03:00
# create a new installation
docker_mariadb_init( )
{
# check dir permissions to reduce likelihood of half-initialized database
ls /docker-entrypoint-initdb.d/ > /dev/null
2023-10-06 13:33:40 +03:00
if [ -n " $DATABASE_INIT_FROM_BACKUP " ] ; then
shopt -s dotglob
for file in /docker-entrypoint-initdb.d/*.tar{ .gz,.xz,.zst} ; do
mkdir -p " $DATADIR " /.init
tar --auto-compress --extract --file " $file " --directory= " $DATADIR " /.init
mariadb-backup --target-dir= " $DATADIR " /.init --datadir= " $DATADIR " /.restore --move-back
mv " $DATADIR " /.restore/** " $DATADIR " /
2023-10-17 11:52:51 +11:00
if [ -f " $DATADIR /.init/backup-my.cnf " ] ; then
mv " $DATADIR /.init/backup-my.cnf " " $DATADIR /.my.cnf "
mysql_note "Adding startup configuration:"
2024-06-20 18:00:53 +10:00
my_print_defaults --defaults-file= " $DATADIR /.my.cnf " --mariadbd
2023-10-06 13:33:40 +03:00
fi
rm -rf " $DATADIR " /.init " $DATADIR " /.restore
2023-10-17 11:52:51 +11:00
if [ " $( id -u) " = "0" ] ; then
# this will cause less disk access than `chown -R`
2024-06-21 13:11:24 +10:00
find " $DATADIR " \! -user mysql \( -exec chown mysql: '{}' + -o -true \)
2023-10-17 11:52:51 +11:00
fi
2023-10-06 13:33:40 +03:00
done
if _check_if_upgrade_is_needed; then
docker_mariadb_upgrade " $@ "
fi
return
fi
2023-10-05 23:16:04 +03:00
docker_init_database_dir " $@ "
mysql_note "Starting temporary server"
docker_temp_server_start " $@ "
mysql_note "Temporary server started."
docker_setup_db
docker_process_init_files /docker-entrypoint-initdb.d/*
# Wait until after /docker-entrypoint-initdb.d is performed before setting
# root@localhost password to a hash we don't know the password for.
if [ -n " ${ MARIADB_ROOT_PASSWORD_HASH } " ] ; then
mysql_note "Setting root@localhost password hash"
docker_process_sql --dont-use-mysql-root-password --binary-mode <<-EOSQL
SET @@SESSION.SQL_LOG_BIN= 0;
SET PASSWORD FOR 'root' @'localhost' = '${MARIADB_ROOT_PASSWORD_HASH}' ;
EOSQL
fi
mysql_note "Stopping temporary server"
docker_temp_server_stop
mysql_note "Temporary server stopped"
echo
mysql_note "MariaDB init process done. Ready for start up."
echo
}
2021-11-19 17:31:42 +11:00
# backup the mysql database
docker_mariadb_backup_system( )
{
if [ -n " $MARIADB_DISABLE_UPGRADE_BACKUP " ] \
&& [ " $MARIADB_DISABLE_UPGRADE_BACKUP " = 1 ] ; then
mysql_note "MariaDB upgrade backup disabled due to \$MARIADB_DISABLE_UPGRADE_BACKUP=1 setting"
return
fi
local backup_db = "system_mysql_backup_unknown_version.sql.zst"
local oldfullversion = "unknown_version"
2024-06-20 18:00:53 +10:00
if [ -r " $DATADIR " /mariadb_upgrade_info ] ; then
read -r -d '' oldfullversion < " $DATADIR " /mariadb_upgrade_info || true
2021-11-19 17:31:42 +11:00
if [ -n " $oldfullversion " ] ; then
backup_db = " system_mysql_backup_ ${ oldfullversion } .sql.zst "
fi
fi
mysql_note " Backing up system database to $backup_db "
2024-06-20 18:00:53 +10:00
if ! mariadb-dump --skip-lock-tables --replace --databases mysql --socket= " ${ SOCKET } " | zstd > " ${ DATADIR } / ${ backup_db } " ; then
2021-11-19 17:31:42 +11:00
mysql_error " Unable backup system database for upgrade from $oldfullversion . "
fi
mysql_note "Backing up complete"
}
# perform mariadb-upgrade
# backup the mysql database if this is a major upgrade
docker_mariadb_upgrade( ) {
if [ -z " $MARIADB_AUTO_UPGRADE " ] \
|| [ " $MARIADB_AUTO_UPGRADE " = 0 ] ; then
2024-06-20 18:00:53 +10:00
mysql_note "MariaDB upgrade (mariadb-upgrade or creating healthcheck users) required, but skipped due to \$MARIADB_AUTO_UPGRADE setting"
2021-11-19 17:31:42 +11:00
return
fi
mysql_note "Starting temporary server"
2022-02-05 09:51:00 +11:00
docker_temp_server_start " $@ " --skip-grant-tables \
2024-09-04 13:44:06 +10:00
--loose-innodb_buffer_pool_dump_at_shutdown= 0
2021-11-19 17:31:42 +11:00
mysql_note "Temporary server started."
docker_mariadb_backup_system
2024-01-24 15:03:55 +11:00
if [ ! -f " $DATADIR " /.my-healthcheck.cnf ] ; then
mysql_note "Creating healthcheck users"
local createHealthCheckUsers
createHealthCheckUsers = $( create_healthcheck_users)
docker_process_sql --dont-use-mysql-root-password --binary-mode <<-EOSQL
-- Healthcheck users shouldn' t be replicated
SET @@SESSION.SQL_LOG_BIN= 0;
-- we need the SQL_MODE NO_BACKSLASH_ESCAPES mode to be clear for the password to be set
SET @@SESSION.SQL_MODE= REPLACE( @@SESSION.SQL_MODE, 'NO_BACKSLASH_ESCAPES' , '' ) ;
FLUSH PRIVILEGES;
$createHealthCheckUsers
EOSQL
mysql_note "Stopping temporary server"
docker_temp_server_stop
mysql_note "Temporary server stopped"
if _check_if_upgrade_is_needed; then
# need a restart as FLUSH PRIVILEGES isn't reversable
mysql_note "Restarting temporary server for upgrade"
docker_temp_server_start " $@ " --skip-grant-tables \
2024-09-04 13:44:06 +10:00
--loose-innodb_buffer_pool_dump_at_shutdown= 0
2024-01-24 15:03:55 +11:00
else
return 0
fi
fi
2021-11-19 17:31:42 +11:00
mysql_note "Starting mariadb-upgrade"
2024-06-20 18:00:53 +10:00
mariadb-upgrade --upgrade-system-tables
2021-11-19 17:31:42 +11:00
mysql_note "Finished mariadb-upgrade"
mysql_note "Stopping temporary server"
2022-09-23 09:27:19 +10:00
docker_temp_server_stop
2021-11-19 17:31:42 +11:00
mysql_note "Temporary server stopped"
}
_check_if_upgrade_is_needed( ) {
2024-06-20 18:00:53 +10:00
if [ ! -f " $DATADIR " /mariadb_upgrade_info ] ; then
2021-11-19 17:31:42 +11:00
mysql_note "MariaDB upgrade information missing, assuming required"
return 0
fi
local mariadbVersion
mariadbVersion = " $( _mariadb_version) "
IFS = '.-' read -ra newversion <<< " $mariadbVersion "
2024-06-20 18:00:53 +10:00
IFS = '.-' read -ra oldversion < " $DATADIR " /mariadb_upgrade_info || true
2021-11-19 17:31:42 +11:00
if [ [ ${# newversion [@] } -lt 2 ] ] || [ [ ${# oldversion [@] } -lt 2 ] ] \
|| [ [ ${ oldversion [0] } -lt ${ newversion [0] } ] ] \
|| [ [ ${ oldversion [0] } -eq ${ newversion [0] } && ${ oldversion [1] } -lt ${ newversion [1] } ] ] ; then
return 0
fi
2024-01-24 15:03:55 +11:00
if [ ! -f " $DATADIR " /.my-healthcheck.cnf ] ; then
mysql_note "MariaDB heathcheck configation file missing, assuming desirable"
return 0
fi
2021-11-19 17:31:42 +11:00
mysql_note "MariaDB upgrade not required"
return 1
}
2024-06-20 18:00:53 +10:00
# check arguments for an option that would cause mariadbd to stop
2019-10-31 16:57:08 -07:00
# return true if there is one
_mysql_want_help( ) {
local arg
for arg; do
case " $arg " in
-'?' | --help| --print-defaults| -V| --version)
return 0
; ;
esac
done
return 1
}
_main( ) {
2024-06-20 18:00:53 +10:00
# if command starts with an option, prepend mariadbd
2019-10-31 16:57:08 -07:00
if [ " ${ 1 : 0 : 1 } " = '-' ] ; then
2024-06-20 18:00:53 +10:00
set -- mariadbd " $@ "
2019-10-31 16:57:08 -07:00
fi
2022-03-07 16:34:11 +11:00
#ENDOFSUBSTITUTIONS
2019-10-31 16:57:08 -07:00
# skip setup if they aren't running mysqld or want an option that stops mysqld
2021-05-27 17:02:45 +10:00
if [ " $1 " = 'mariadbd' ] || [ " $1 " = 'mysqld' ] && ! _mysql_want_help " $@ " ; then
2021-03-16 13:15:36 +11:00
mysql_note " Entrypoint script for MariaDB Server ${ MARIADB_VERSION } started. "
2019-10-31 16:57:08 -07:00
mysql_check_config " $@ "
# Load various environment variables
docker_setup_env " $@ "
docker_create_db_directories
# If container is started as root user, restart as dedicated mysql user
if [ " $( id -u) " = "0" ] ; then
mysql_note "Switching to dedicated user 'mysql'"
2021-12-06 14:30:12 +11:00
exec gosu mysql " ${ BASH_SOURCE [0] } " " $@ "
2015-08-11 16:39:56 -07:00
fi
2019-10-31 16:57:08 -07:00
# there's no database, so it needs to be initialized
if [ -z " $DATABASE_ALREADY_EXISTS " ] ; then
docker_verify_minimum_env
2020-02-28 16:14:54 -08:00
2023-10-05 23:16:04 +03:00
docker_mariadb_init " $@ "
2021-11-19 17:31:42 +11:00
# MDEV-27636 mariadb_upgrade --check-if-upgrade-is-needed cannot be run offline
2024-06-20 18:00:53 +10:00
#elif mariadb-upgrade --check-if-upgrade-is-needed; then
2021-11-19 17:31:42 +11:00
elif _check_if_upgrade_is_needed; then
docker_mariadb_upgrade " $@ "
2019-10-31 16:57:08 -07:00
fi
2014-11-24 15:31:55 -08:00
fi
2019-10-31 16:57:08 -07:00
exec " $@ "
}
2014-11-24 15:31:55 -08:00
2019-10-31 16:57:08 -07:00
# If we are sourced from elsewhere, don't perform any further actions
if ! _is_sourced; then
_main " $@ "
fi