Support for Docker image MySQL

 

Application: MySQL - https://www.mysql.com/

Docker Hub: https://hub.docker.com/_/mysql

GitHub: https://github.com/mysql

Documentation: https://dev.mysql.com/doc/

 

Overview:

 

Official MySQL database container. It allows to set a database and username without using the console.

 

#Root Password:
This container creates by default a random root password on initial execution. Open Docker > MariaDB Icon > Logs > Scroll down to "GENERATED ROOT PASSWORD" to find it.

 

#Creating database dumps
docker exec some-mysql sh -c 'exec mysqldump --all-databases -uroot -p"$MYSQL_ROOT_PASSWORD"' > /mnt/user/Backups/all-databases.sql

 

#Restoring data from dump files
docker exec -i some-mysql sh -c 'exec mysql -uroot -p"$MYSQL_ROOT_PASSWORD"' < /mnt/user/Backups/all-databases.sql

 

#Configuration without a cnf file
Many configuration options can be passed as flags to mysqld. This will give you the flexibility to customize the container without needing a cnf file. For example, if you want to change the default encoding and collation for all tables to use UTF-8 (utf8mb4) just append the following to the Post Arguments:

 

--character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci

 

Here is a list of all Server System Variables -> https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html

 

#Repository tags:
If you want to install a specific version of mysql, you can simply customize the repository. For example:

 

mysql (is the same like mysql:latest)
mysql:5.7
mysql:8.2.0

Edited March 18, 20242 yr by UNRA1DUser

Hi,

I need to add/change a line to `my.cnf`

secure-file-priv = ""

 

I can find the file by clicking on the docker icon, starting the console and typing `ls -l etc/my.cnf`

`-rw-r--r-- 1 root root 1319 Feb 14 02:55 etc/my.cnf`

 

Now we need to edit the file?

Also if able to edit and save, will the changes persist across updates?

 

Or get what you say above to work "#Configuration without a cnf file"

"just append the following to the Post Arguments" - where are the post args to append to, can you provide a screenshot or clarification?

 

In my case, to verify this setting, in MySQL workbench `SHOW VARIABLES LIKE "secure_file_priv";`

 

Thanks

 

UPDATE:

OK worked it out, Edit the docker, at the top change from 'basic view' to 'advanced view' you will then be able to see 'Post Arguments:'

 

click apply, the docker auto restarts

 

Done...

Edited March 2, 20242 yr by GigaTech
Update

On 3/2/2024 at 6:01 PM, GigaTech said:

Hi,

I need to add/change a line to `my.cnf`

secure-file-priv = ""

 

I can find the file by clicking on the docker icon, starting the console and typing `ls -l etc/my.cnf`

`-rw-r--r-- 1 root root 1319 Feb 14 02:55 etc/my.cnf`

 

Now we need to edit the file?

Also if able to edit and save, will the changes persist across updates?

 

Or get what you say above to work "#Configuration without a cnf file"

"just append the following to the Post Arguments" - where are the post args to append to, can you provide a screenshot or clarification?

 

In my case, to verify this setting, in MySQL workbench `SHOW VARIABLES LIKE "secure_file_priv";`

 

Thanks

 

UPDATE:

OK worked it out, Edit the docker, at the top change from 'basic view' to 'advanced view' you will then be able to see 'Post Arguments:'

 

click apply, the docker auto restarts

 

Done...

 

Sorry for my late response! Yes it´s under the 'advanced view'. I'm glad this has helped.

 

If you remove the "mysqld --log-error=/var/log/mysql/error.log" out of the Post Arguments you wouldn´t get any kind of logs into the folder. Maybe try mysqld --log-error=/var/log/mysql/error.log --secure-file-priv=""

I have NOT removed anything, the value was empty, just added my arg to it and sent pic?

 

I have MySQL container running along with adminer container.  I can connect to MySQL from Adminer, but can't connect from vBulletin running in a VM.  The VM is on the same network with unraid.  It's able to connect to a local copy of mysql just, fine, but when i point it to the MySQL container it doesn't connect.

 

Any ideas?

 

Thanks,

James

 

On 5/14/2024 at 7:48 AM, heisenfig said:

I have MySQL container running along with adminer container.  I can connect to MySQL from Adminer, but can't connect from vBulletin running in a VM.  The VM is on the same network with unraid.  It's able to connect to a local copy of mysql just, fine, but when i point it to the MySQL container it doesn't connect.

 

Any ideas?

 

Thanks,

James

 

On which Network are those Dockers ?

I upgraded my vBulletin5 to the latest V5 version and it was able to connect then.

this is a really poorly designed image for being official, doesn't work very well.  it can't even be connected to from outside the container the documentation is awful.  

Edited July 21, 20241 yr by oliver

I try to connect with the docker "Apache-php" and also "Nginx-PHP8". with both I can't connect to the DB but it works with adminer.

With Apache I get this error :

SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

 

With Nginx I get this error :

SQLSTATE[HY000] [2002] No such file or directory

 

 

Some have an idea ? thx !

2024-09-22T15:38:54.375857Z 0 [ERROR] [MY-013901] [InnoDB] Failed to resize unused redo log file ./#innodb_redo/#ib_redo17_tmp to 3 MB (Failed to find the file).
2024-09-22T15:38:54.406680Z 0 [ERROR] [MY-012891] [InnoDB] Failed to create redo log file ./#innodb_redo/#ib_redo17 (error: 1504) for start LSN 55678976
2024-09-22T15:38:54.406786Z 0 [ERROR] [MY-013864] [InnoDB] [FATAL] Error 1504 encountered when writing to the redo log file: ./#innodb_redo/#ib_redo16.
2024-09-22T15:38:54.406818Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0write.cc:2110:ib::fatal triggered thread 22772013979200
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/9.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2024-09-22T15:38:54Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=28011a04ecffb589c6a1d0499f9e5eae6c552217
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x100000
 #0 0xc5625e <unknown>
 #1 0x16840ed <unknown>
 #2 0x18393fc <unknown>
 #3 0x1851854 <unknown>
 #4 0x177ed14 <unknown>
 #5 0x1789129 <unknown>
 #6 0x178a467 <unknown>
 #7 0x17790e8 <unknown>
 #8 0x14b61b0dbad3 <unknown>
 #9 0x14b61ac89c11 <unknown>
 #10 0x14b61ad0df53 <unknown>
 #11 0xffffffffffffffff <unknown>
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2024-09-22T15:38:58.650451Z 0 [System] [MY-015017] [Server] MySQL Server Initialization - start.
2024-09-22T15:38:58.652105Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 9.0.1) initializing of server in progress as process 41
2024-09-22T15:38:58.653975Z 0 [ERROR] [MY-010457] [Server] --initialize specified but the data directory has files in it. Aborting.
2024-09-22T15:38:58.654009Z 0 [ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it.
2024-09-22T15:38:58.654197Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-09-22T15:38:58.654611Z 0 [System] [MY-015018] [Server] MySQL Server Initialization - end.
2024-09-22T15:38:59.702866Z 0 [System] [MY-015017] [Server] MySQL Server Initialization - start.
2024-09-22T15:38:59.704693Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 9.0.1) initializing of server in progress as process 41
2024-09-22T15:38:59.706570Z 0 [ERROR] [MY-010457] [Server] --initialize specified but the data directory has files in it. Aborting.
2024-09-22T15:38:59.706604Z 0 [ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it.
2024-09-22T15:38:59.706718Z 0 [ERROR] [MY-010119] [Server] Aborting

 

 

Hello everyone, my MySQL Docker container just crashed after several poorly formatted INSERT INTO queries. I can't restart it anymore, the console and logs open and close instantly. I saw errors in the logs. Of course, I didn't have time to make a backup... Then I made a mistake, I restarted the setup of this addon, which erased all the files, so I really lost everything. I saw that the memory was limited to 2GB during installation, could it be due to that?

 

Thank you !

Hi, another full crash

Shutdown by "appdata backup" addon

 

Any solution to avoid this please ?

 

Thank you !

 

2024-09-23T03:01:06.395201Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 9.0.1).
2024-09-23T03:01:07.211793Z 0 [ERROR] [MY-012592] [InnoDB] Operating system error number 2 in a file operation.
2024-09-23T03:01:07.211992Z 0 [ERROR] [MY-012593] [InnoDB] The error means the system cannot find the path specified.
2024-09-23T03:01:07.212074Z 0 [ERROR] [MY-012646] [InnoDB] File ./#innodb_redo/#ib_redo9: 'rename' returned OS error 71.
2024-09-23T03:01:07.212099Z 0 [ERROR] [MY-013905] [InnoDB] Failed to mark redo log file ./#innodb_redo/#ib_redo9 as unused (by renaming to ./#innodb_redo/#ib_redo9_tmp).
2024-09-23T03:01:07.778349Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 9.0.1)  MySQL Community Server - GPL.
2024-09-23T03:01:07.778449Z 0 [System] [MY-015016] [Server] MySQL Server - end.
2024-09-23T03:01:12.200040Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2024-09-23T03:01:12.405024Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 9.0.1) starting as process 1
2024-09-23T03:01:12.407165Z 0 [Warning] [MY-010122] [Server] One can only use the --user switch if running as root
2024-09-23T03:01:12.408890Z 0 [Warning] [MY-010075] [Server] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 1723ed64-7958-11ef-857c-0242ac110007.
2024-09-23T03:01:12.419828Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-09-23T03:01:13.070397Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-09-23T03:01:13.265804Z 1 [Warning] [MY-012351] [InnoDB] Tablespace 1, name 'sys/sys_config', file './sys/sys_config.ibd' is missing!
mysqld: File './binlog.000001' not found (OS errno 2 - No such file or directory)
2024-09-23T03:01:13.536061Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2024-09-23T03:01:14.466988Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-09-23T03:01:14.467031Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-09-23T03:01:14.734596Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
2024-09-23T03:01:14.769901Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2024-09-23T03:01:14.770099Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '9.0.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.
2024-09-24T03:01:06.198187Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 9.0.1).
2024-09-24T03:01:07.660186Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 9.0.1)  MySQL Community Server - GPL.
2024-09-24T03:01:07.660242Z 0 [System] [MY-015016] [Server] MySQL Server - end.
2024-09-24T03:01:13.185240Z 0 [System] [MY-015017] [Server] MySQL Server Initialization - start.
2024-09-24T03:01:13.186906Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 9.0.1) initializing of server in progress as process 41
2024-09-24T03:01:13.188804Z 0 [ERROR] [MY-010457] [Server] --initialize specified but the data directory has files in it. Aborting.
2024-09-24T03:01:13.188838Z 0 [ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it.
2024-09-24T03:01:13.188908Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-09-24T03:01:13.189399Z 0 [System] [MY-015018] [Server] MySQL Server Initialization - end.

 

Hi friends, 

 

i have mysql docker which shows me this error:

   packet.raise_for_error()
  File "Z:\TW22Pycharm\.venv\Lib\site-packages\pymysql\protocol.py", line 219, in raise_for_error
    err.raise_mysql_exception(self._data)
  File "Z:\TW22Pycharm\.venv\Lib\site-packages\pymysql\err.py", line 150, in raise_mysql_exception
    raise errorclass(errno, errval)
pymysql.err.InternalError: (3, "Error writing file '/tmp/MLfd=147' (OS errno 28 - No space left on device)")

Process finished with exit code 1

 

I believe it is due to mysql engine is writing tmp files directly in the container, i.e. in docker image.

 

But why those files are left in docker even if I do db commit after each sql update?

 

CAn you advice?

 

Thanks

 

V

I recently updated my docker container to the latest, and it wasn't until a few days later that I realised the upgrade had corrupted a database (unsure which one) and I am now unable to start the DB. 

The container logs are lots of this:

 

2025-01-08T09:37:08.031157Z 1 [ERROR] [MY-012202] [InnoDB] Tablespace ID: 106 = ['data/nextcloud/oc_users.ibd', 'nextcloud/oc_files_reminders.ibd'] 
2025-01-08T09:37:08.031161Z 1 [ERROR] [MY-012202] [InnoDB] Tablespace ID: 4294967278 = ['data/undo_002', 'undo_002'] 
2025-01-08T09:37:08.031168Z 1 [ERROR] [MY-012202] [InnoDB] Tablespace ID: 4294967279 = ['data/undo_001', 'undo_001'] 
2025-01-08T09:37:08.031172Z 1 [ERROR] [MY-012202] [InnoDB] Tablespace ID: 4294967294 = ['data/mysql.ibd', 'mysql.ibd'] 
2025-01-08T09:37:08.031200Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Failed, retry may succeed.
2025-01-08T09:37:08.031259Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2025-01-08T09:37:08.031343Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2025-01-08T09:37:08.031355Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-01-08T09:37:08.032354Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.0)  MySQL Community Server - GPL.
2025-01-08T09:37:08.032361Z 0 [System] [MY-015016] [Server] MySQL Server - end.

 

 

And the error log within the containers directory looks like this:

 

2024-09-01T11:23:49.139075Z 0 [System] [MY-015016] [Server] MySQL Server - end.
2024-09-01T11:23:49.660883Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2024-09-01T11:23:49.865552Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.0) starting as process 1
2024-09-01T11:23:49.866700Z 0 [Warning] [MY-010122] [Server] One can only use the --user switch if running as root
2024-09-01T11:23:49.869405Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-09-01T11:23:49.992103Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-09-01T11:23:50.177701Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-09-01T11:23:50.177730Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-09-01T11:23:50.182927Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
2024-09-01T11:23:50.203895Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.4.0'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.
2024-09-01T11:23:50.457721Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2024-09-01T11:26:31.878111Z 0 [ERROR] [MY-011906] [InnoDB] Database page corruption on disk or a failed file read of page [page id: space=4294967293, page number=3]. You may have to recover from a backup.

 

 

 

Then after a bit of research, it seems like I need to run the innodb-recovery tool as shown here: https://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html

 

However the container directory does not contain the my.conf file that it is referring to, so I have no idea where to put this [mysqld] innodb_force_recovery = 1 line.

 

Has anyone come across this? Extremely frustrating

I'm trying to access the database from the console of mysql but I am getting an access denied for my user. The password is the random generated one I received and the username and everything is correct. Unsure on what is happening as I can't access it neither from the console nor from DBeaver.

Hey, any ideas how to get mysql_native_password working with this docker?
I've tried adding these separately & together to post arguments and the docker just reboot loops.

--mysql_native_password=ON
--default_authentication_plugin=mysql_native_password

Also tried adding the variable to the docker.
MYSQL_AUTHENTICATION_PLUGIN
mysql_native_password

That cnf file that I could just edit sure would be useful right now 😂

EDIT: The owner hasn't been online in 6 months... looks like we aren't getting any support here.

Edited June 9, 20251 yr by DanW

19 hours ago, DanW said:

Hey, any ideas how to get mysql_native_password working with this docker?
I've tried adding these separately & together to post arguments and the docker just reboot loops.

--mysql_native_password=ON
--default_authentication_plugin=mysql_native_password

Also tried adding the variable to the docker.
MYSQL_AUTHENTICATION_PLUGIN
mysql_native_password

That cnf file that I could just edit sure would be useful right now 😂

EDIT: The owner hasn't been online in 6 months... looks like we aren't getting any support here.

I ended up using mysql:5.7 as the repo.

EDIT Solved:

Issue :
version : 9.5.0

edition : MySQL Community Server - GPL

log_bin : 1 ← binary log ON

binlog_format: ROW

gtid_mode : ON ← GTID ON

enforce_gtid_consistency: ON

So your MySQL is strict GTID + binlog = ON, which does not like what Spotweb’s retrieve code is doing, and that’s why it keep getting:

Statement violates GTID consistency: Updates to non-transactional tables...

This MySQL config itself will keep breaking Spotweb.

I've created a file zz-spotweb-gtid.cnf chmod 644 with the following lines:
log_bin=0

skip_log_bin=1

gtid_mode=OFF

enforce_gtid_consistency=OFF

In UnRAID:

1. Go to Docker → click on mysql-spotweb → Edit.

2. Add a new Path mapping:

   • Host path:
     /mnt/user/appdata/mysql-spotweb/zz-spotweb-gtid.cnf

   • Container path:
     /etc/mysql/conf.d/zz-spotweb-gtid.cnf

   • Access mode: Read-only

and restart the mysql docker.

What is causing my Spotweb to crash with this error? It this related to the mysql DB?

SpotWeb v0.68.38.34 on PHP v8.3.27 crashed

Fatal error occured during retrieve:

HY000: 1785: Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.

#0 /var/www/spotweb/lib/dbeng/dbeng_pdo.php(86): dbeng_pdo->exec()

#1 /var/www/spotweb/lib/dao/Mysql/Dao_Mysql_Spot.php(51): dbeng_pdo->modify()

#2 /var/www/spotweb/lib/services/Retriever/Services_Retriever_Spots.php(656): Dao_Mysql_Spot->removeSpots()

#3 /var/www/spotweb/lib/services/Retriever/Services_Retriever_Base.php(239): Services_Retriever_Spots->process()

#4 /var/www/spotweb/lib/services/Retriever/Services_Retriever_Base.php(340): Services_Retriever_Base->loopTillEnd()

#5 /var/www/spotweb/retrieve.php(142): Services_Retriever_Base->perform()

#6 {main}

Finished retrieving spots.

Edited November 20, 2025Nov 20 by TallMan206

On 11/19/2025 at 11:20 PM, TallMan206 said:

EDIT Solved:

Issue :
version : 9.5.0

edition : MySQL Community Server - GPL

log_bin : 1 ← binary log ON

binlog_format: ROW

gtid_mode : ON ← GTID ON

enforce_gtid_consistency: ON

So your MySQL is strict GTID + binlog = ON, which does not like what Spotweb’s retrieve code is doing, and that’s why it keep getting:

Statement violates GTID consistency: Updates to non-transactional tables...

This MySQL config itself will keep breaking Spotweb.

I've created a file zz-spotweb-gtid.cnf chmod 644 with the following lines:
log_bin=0

skip_log_bin=1

gtid_mode=OFF

enforce_gtid_consistency=OFF

In UnRAID:

1. Go to Docker → click on mysql-spotweb → Edit.

2. Add a new Path mapping:

   • Host path:
     /mnt/user/appdata/mysql-spotweb/zz-spotweb-gtid.cnf

   • Container path:
     /etc/mysql/conf.d/zz-spotweb-gtid.cnf

   • Access mode: Read-only

and restart the mysql docker.

What is causing my Spotweb to crash with this error? It this related to the mysql DB?

SpotWeb v0.68.38.34 on PHP v8.3.27 crashed

Fatal error occured during retrieve:

HY000: 1785: Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.

#0 /var/www/spotweb/lib/dbeng/dbeng_pdo.php(86): dbeng_pdo->exec()

#1 /var/www/spotweb/lib/dao/Mysql/Dao_Mysql_Spot.php(51): dbeng_pdo->modify()

#2 /var/www/spotweb/lib/services/Retriever/Services_Retriever_Spots.php(656): Dao_Mysql_Spot->removeSpots()

#3 /var/www/spotweb/lib/services/Retriever/Services_Retriever_Base.php(239): Services_Retriever_Spots->process()

#4 /var/www/spotweb/lib/services/Retriever/Services_Retriever_Base.php(340): Services_Retriever_Base->loopTillEnd()

#5 /var/www/spotweb/retrieve.php(142): Services_Retriever_Base->perform()

#6 {main}

Finished retrieving spots.

This worked perfectly for me to solve my issues since the latest update, thanks so much!

Edited January 4Jan 4 by ianb85