December 8, 2025Dec 8 Hello everyone.First of all: I used a translator. I hope you can understand everything.I updated everything to the latest versions (Unraid, apps, Docker). This includes Nextcloud and MariaDB. Since then, the Nextcloud client seems to only sync document changes in one direction (from PC to server), but as soon as I make changes in the browser or on my phone, it no longer pulls the data back to the PC. So I started looking into it and found the following error message in the Nextcloud admin area:Database versionDetected MariaDB version "12.1.2-MariaDB-ubu2404". For optimal performance, stability, and functionality with this version of Nextcloud, MariaDB >= 10.6 and <= 11.8 is recommended.Is there an easy way to roll back the MariaDB Docker container to, for example, version 11.8? I assume you can simply change the image source for the Docker container (currently set to "mariadb"), but I don’t want to break anything and I’m not sure what exactly I should enter there…Thanks for help!
December 8, 2025Dec 8 Author 21 minutes ago, DarkInception said:Is there an easy way to roll back the MariaDB Docker container to, for example, version 11.8? IThis is not possible. You need to export the nextcloud database to sql as root user (execute this inside the container terminal):mariadb-dump -u root -p --single-transaction --routines --events --triggers nextcloud >/var/lib/mysql/nextcloud.$(date +"%F-%H-%M-%S").sqlNow stop the mariadb container and rename the appdata path through the file manager or through the unraid terminal:mv /mnt/user/appdata/mariadb /mnt/user/appdata/mariadb_oldNow select the add container button on the docker page, select your mariadb template from the drop-down and do this:Change the name e.g. nextcloud-mariadb (important)Change the repository name to mariadb:11.8Press OK to install it.Now, check the logs and copy the new root password.Copy the nextcloud.sql file through the file manager or unraid terminal as follows:cp -a /mnt/user/appdata/mariadb_old/data/nextcloud*.sql /mnt/user/app data/mariadb/data/nextcloud.sqlOpen the mariadb container and import the database as follows:mariadb -u root -p nextcloud < /var/lib/mysql/nextcloud.sqlI did this by myself a few weeks ago. My database is currently fixed to version 11.4 because of that:A possible alternative to those commands is to install phpmyadmin or a similar db webgui. Or use HeidiSQL if you prefer an app.
December 8, 2025Dec 8 Thank you very much for the quick help! It worked wonderfully!Of course, I had to check the paths a bit to see if they really have the same names on my system (on my system, there was always an “mariadb-official” in appdata). But with these adjustments, it worked perfectly and the notification in Nextcloud is gone.
December 13, 2025Dec 13 Running the latest version of this docker container on unraid 7.2.2, I am unable to login as root. I've set my own password, allowed it to randomly generate but no matter what I do it says denied. I even set the password to password as a test and it said it was wrong despite printing it in the logs.Any idea what's going on?Update: Self Resolved. When i deleted my old instance it didn't delete its directory in appdata. When I installed the new instance the old directory cause erratic behavior. Deleted the docker container, deleted the directory, reinstalled and its happy now. Edited December 13, 2025Dec 13 by supawiz6991
January 30Jan 30 On 6/10/2021 at 8:33 AM, mgutt said:Set Root Password If you like to manually set your root password remove the word "yes" from "Generate Random Password": Then set your password through "Show more settings": Note: This does not allow to change the password. Reset Root Password Edit the container, enable advanced view and add "mysqld_safe --skip-grant-tables" to the Post Arguments and start the container: Open the cotnainer's console and execute the following commands:mariadb -u root Now you are connected to MariaDB. Execute this:FLUSH PRIVILEGES; And finally this:SET PASSWORD FOR root@'localhost' = PASSWORD('your_new_password'); Finally edit the container and remove the "mysqld_safe --skip-grant-tables" part again.These steps don't appear to work any more. Setting the skip grant tables option forces the process to exit on startup. Is there a solution already to this?Following suggestions made previously, here is what happens with the advised setup, also the same output as using mariadb-safe instead of mysqld_safe (the recommendation another user made):root@Harris:/mnt/user/grafana-data# docker logs -f mariadb [migrations] started [migrations] no migrations found ─────────────────────────────────────── ██╗ ███████╗██╗ ██████╗ ██║ ██╔════╝██║██╔═══██╗ ██║ ███████╗██║██║ ██║ ██║ ╚════██║██║██║ ██║ ███████╗███████║██║╚██████╔╝ ╚══════╝╚══════╝╚═╝ ╚═════╝ Brought to you by linuxserver.io ─────────────────────────────────────── To support LSIO projects visit: https://www.linuxserver.io/donate/ ─────────────────────────────────────── GID/UID ─────────────────────────────────────── User UID: 99 User GID: 100 ─────────────────────────────────────── Linuxserver.io version: 11.4.8-r0-ls203 Build-date: 2026-01-20T07:53:31+00:00 ─────────────────────────────────────── [custom-init] No custom files found, skipping... UMASK must be a 3-digit mode with an additional leading 0 to indicate octal. The first digit will be corrected to 6, the others may be 0, 2, 4, or 6. UMASK corrected from 022 to 0640 ... Warning: World-writable config file '/config/custom.cnf' is ignored Warning: World-writable config file '/config/custom.cnf' is ignored 260130 18:39:59 mysqld_safe Logging to '/config/databases/1c674088524c.err'. 260130 18:39:59 mysqld_safe Starting mariadbd daemon with databases from /config/databases Connection to localhost (::1) 3306 port [tcp/mysql] succeeded! ##################################################################################### # # # Logrotate Instructions # # # # Add the following to /config/custom.cnf under [mysqld]: # # log_error = /config/log/mysql/mariadb-error.log # # # # Login to the SQL shell inside the container using: # # mariadb -uroot -p<PASSWORD> # # And run the following command: # # GRANT ALL ON *.* TO root@localhost IDENTIFIED VIA unix_socket WITH GRANT OPTION ; # # # # Restart the container to apply the changes. # # # # You can read more about root@localhost permissions here: # # https://mariadb.com/kb/en/authentication-from-mariadb-10-4/ # # # ##################################################################################### [ls.io-init] done. /usr/bin/mysqld_safe: Deprecated program name. It will be removed in a future release, use 'mariadbd-safe' instead 260130 18:40:00 mysqld_safe Logging to '/var/lib/mysql/1c674088524c.err'. 260130 18:40:00 mysqld_safe Starting mariadbd daemon with databases from /var/lib/mysql Caught SIGTERM signal!And if I try to add only --skip-grant-tables:root@Harris:/mnt/user/grafana-data# docker logs -f mariadb [migrations] started [migrations] no migrations found ─────────────────────────────────────── ██╗ ███████╗██╗ ██████╗ ██║ ██╔════╝██║██╔═══██╗ ██║ ███████╗██║██║ ██║ ██║ ╚════██║██║██║ ██║ ███████╗███████║██║╚██████╔╝ ╚══════╝╚══════╝╚═╝ ╚═════╝ Brought to you by linuxserver.io ─────────────────────────────────────── To support LSIO projects visit: https://www.linuxserver.io/donate/ ─────────────────────────────────────── GID/UID ─────────────────────────────────────── User UID: 99 User GID: 100 ─────────────────────────────────────── Linuxserver.io version: 11.4.8-r0-ls203 Build-date: 2026-01-20T07:53:31+00:00 ─────────────────────────────────────── [custom-init] No custom files found, skipping... UMASK must be a 3-digit mode with an additional leading 0 to indicate octal. The first digit will be corrected to 6, the others may be 0, 2, 4, or 6. UMASK corrected from 022 to 0640 ... Warning: World-writable config file '/config/custom.cnf' is ignored Warning: World-writable config file '/config/custom.cnf' is ignored 260130 18:41:09 mysqld_safe Logging to '/config/databases/3941b1a7fd4f.err'. 260130 18:41:09 mysqld_safe Starting mariadbd daemon with databases from /config/databases Connection to localhost (::1) 3306 port [tcp/mysql] succeeded! ##################################################################################### # # # Logrotate Instructions # # # # Add the following to /config/custom.cnf under [mysqld]: # # log_error = /config/log/mysql/mariadb-error.log # # # # Login to the SQL shell inside the container using: # # mariadb -uroot -p<PASSWORD> # # And run the following command: # # GRANT ALL ON *.* TO root@localhost IDENTIFIED VIA unix_socket WITH GRANT OPTION ; # # # # Restart the container to apply the changes. # # # # You can read more about root@localhost permissions here: # # https://mariadb.com/kb/en/authentication-from-mariadb-10-4/ # # # ##################################################################################### [ls.io-init] done. /run/s6/basedir/scripts/rc.init: line 91: --skip-grant-tables: not foundAnother edit:Just tried adding skip-grant-options to custom.cnf, still no luck. Everything starts up, but no dice getting in. It still demands a password. Edited January 30Jan 30 by TheJoshGriffith
February 7Feb 7 This might have been brought up before, though I wasn't able to find it in this thread.I need a mysql DB and why not use this mariadb docker, so I installed it in Unraid. It couldn't start though, complaining that it wasn't able to write into /tmp/<somerandomname>, due to "Permission denied". As a quick fix I gave everyone full permissions to everything under the mariadb docker folder in appdata (777). To my surprise it did not change anything.Then I went to delete the docker.img file, create a new one, and added all my containers again, and now the mariadb docker was working (with default permissions on the appdata folder, 99:100 755). I started to make use of the mariadb for an application.Thinking it was solved I came back today and started the mariadb docker only to be met by the same error - it can't write to the /tmp folder. Which is weird as that folder is not being mapped as a volume in the configuration of the container, which I actually just noticed now.I just tried adding this as a volume, and that seemed to fix that issue. Instead I'm now met with another error upon starting the container:[ERROR] Can't start server : Bind on unix socket: Permission deniedI realized this is caused by the fact that the server wants to bind a socket on 0.0.0.0, which of course shouldn't be allowed for a container to do. Instead I created a .cnf file in the config folder to bind only to the container's own IP. This seems to solve the issue as it now creates the socket on the IP - but still isn't able to bind on the unix socket. I now get these logs:2026-02-07 18:17:06 0 [Note] Server socket created on IP: 'xx.xx.xx.xx', port: '3306'.2026-02-07 18:17:06 0 [ERROR] Can't start server : Bind on unix socket: Permission denied2026-02-07 18:17:06 0 [ERROR] Do you already have another server running on socket: /run/mysqld/mysqld.sock ?Actually I'm wrong in the above - it is the unix socket it cannot bind on, not the IP. So what's up with this mariadb container - what am I doing wrong? Why can't it do it's very basic thing (its a mariadb container) to start the mariadb service, binding on the socket only found within the container itself? I actually have a hard time believing this, it seems pretty pointless to me, uploading a container like this - I might as well build my own mysql/mariadb container then.Please correct me if I'm wrong ! Edited February 7Feb 7 by captainjee
June 29Jun 29 On 12/13/2025 at 1:15 AM, supawiz6991 said:Running the latest version of this docker container on unraid 7.2.2, I am unable to login as root. I've set my own password, allowed it to randomly generate but no matter what I do it says denied. I even set the password to password as a test and it said it was wrong despite printing it in the logs.Any idea what's going on?Update: Self Resolved. When i deleted my old instance it didn't delete its directory in appdata. When I installed the new instance the old directory cause erratic behavior. Deleted the docker container, deleted the directory, reinstalled and its happy now.Thanks for this! I had lost all my Docker images from my initial setup of Unraid (when I was installing everything), and apparently had set up MariaDB earlier (primarily use PostgreSQL due to using that at work), so the original files remained in appdata, preventing me from changing the password, even with deleting the Docker and image. Thus, it never output the GENERATED ROOT PASSWORD in the logs when I'd start up a new image.
20 hours ago20 hr Hello all!This is for mariaDB and not for phpmyadmin: can anyone please hint me to the correct support thread for phpmyadmin on UNRAID?There are a lot of updates for this docker and I just wanted to use it again after several weeks, but I can not connect to the server anymore.I think the empty server field is the problem, but what went wrong? I did not touch anything, except the updates :) Many thanks for any help!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.