grooverdan
commented
11 months ago The problem with rm -rf /var/lib/mysql/** is it ignore .* files as below (and see man bash):
$ mkdir mysql
/tmp
$ touch mysql/.my_healthcheck.cnf
/tmp
$ rm -rf mysql/**
/tmp
$ ls -la mysql
total 0
drwxr-xr-x. 2 dan dan 60 Jul 19 13:34 .
drwxrwxrwt. 29 root root 820 Jul 19 13:34 ..
-rw-r--r--. 1 dan dan 0 Jul 19 13:34 .my_healthcheck.cnf
/tmp
$ man rm
/tmp
$ rm -rf mysql/** mysql/.*
/tmp
$ ls -la mysql
total 0
drwxr-xr-x. 2 dan dan 40 Jul 19 13:36 .
drwxrwxrwt. 29 root root 820 Jul 19 13:36 ..So to remove you'll need rm -rf /var/lib/mysql/** /var/lib/mysql/.*
Alternately enable shopt -s dotglob like:
$ shopt -s dotglob
/tmp
$ ls -la mysql
total 0
drwxr-xr-x. 2 dan dan 60 Jul 19 13:40 .
drwxrwxrwt. 29 root root 820 Jul 19 13:42 ..
-rw-r--r--. 1 dan dan 0 Jul 19 13:40 .my_healthcheck.cnf
/tmp
$ rm -rf mysql/**
/tmp
$ ls -la mysql
total 0
drwxr-xr-x. 2 dan dan 40 Jul 19 13:42 .
drwxrwxrwt. 29 root root 820 Jul 19 13:42 ..That said, restoring from a full backup in /docker-entrypoint-initdb.d is a pretty common use case and requiring users like yourself to script this manual isn't a great experience. You're pretty luck your data fits in /tmp but larger restores may not be as lucky and --move-back across filesystems is a fully copy again.
If you can come up with a good well known name mariadb-initdb{something}{compressext} (and format - prepare needs to be already done, so just tar?) that if it exists in /docker-entrypoint-initdb.d, and the datadir is empty, its used for the database initialization directly.
I also recommend applying prepare to before the backup was made as a version bump on the mariadb container may not support the prepare stage of the previous backup.
mholmesbeatport
dr-m
I have ran into an issue with getting our local api development environment up and running with our mariadb 10.5 docker container.
I am successful with getting our dev environment up on versions 10.5.18, 10.5.19 and 10.5.20 but since I have 10.5 in my docker-compose file it defaults to the current 10.5.21 version of mariadb.
I have a compressed backup file and an
import.shbash shell file copied into the docker-entrypoint-initdb.d When the container starts the bash shell file is executed and does the following:zstd -d -c /docker-entrypoint-initdb.d/backup.zst | mbstream -x -C /tmprm-rf /var/lib/mysql/**mariabackup --prepare --target-dir=/tmpmariabackup --move-back --target-dir=/tmpThe database files are then moved into the /var/lib/mysql default data directory.
This process works flawlessly in versions <=10.5.20. In version 10.5.21 this process fails because there is now a
.my-healthcheck.cnffile in the /var/lib/mysql data directory. I get the following error: "Original data directory /var/lib/mysql is not empty!"This causes the container to be in a repeating restart loop and fails to start successfully.
This is the docker logs with some added [DEBUG] statements:
I see the
.my-healthcheck.cnffile has been recently implemented approximately 3 weeks ago with the following commit: https://github.com/MariaDB/mariadb-docker/pull/508/files#diff-7325bb1235108b46404c9b33b577ca3033e5d8b65a506b657e41ebccb96fcb5fMentioned in the following GitHub issue: https://github.com/MariaDB/mariadb-docker/issues/512#issuecomment-1608744838
As stated in MariaDB documentation in order to restore a backup the data directory needs to be empty: https://mariadb.com/kb/en/full-backup-and-restore-with-mariabackup/#restoring-the-backup
Any advice on how to work around this is much appreciated!