MYSQLDUMP_OPTS doesn't work about mysql-backup HOT 5 CLOSED

That is one step forward then. Let's close out this issue and open a new one on the Couldn't execute...

Run it in DEBUG mode and paste the output.

Additionally after switching images I had to add user: "0" to backup image.

That isn't a bug, it is by design. A database backup tool should not run as UID 0. If you need it, there could very well be a reason, but we don't want it like that as default.

from mysql-backup.

I have tried with the following option as well without success:

 - MYSQLDUMP_OPTS="--lock-tables=false"

That's how it is documented I think.

debug output is: mysqldump: unknown variable 'OPTS="--lock-tables=false"'

Could you show a working example or give any hints what might be wrong?

from mysql-backup.

Are you using an out of date version? This all was moved over to databack/mysql-backup a while back, yet your compose file references deitch/mysql-backup. Try that. If it doesn't work, turn on DEBUG mode and paste the output (or, if too big, a gist).

To preempt the question, I have wanted docker hub to have a "re-parent" (i.e. redirect) for a long time. It is my hope that I will get it at some point...

from mysql-backup.

After switching to databack/mysql-backup the old error seems to be gone.

However in the logs I can see mysqldump: Couldn't execute 'SHOW PACKAGE STATUS WHERE Db = 'test'': You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'PACKAGE STATUS WHERE Db = 'test'' at line 1 (1064).

Additionally after switching images I had to add user: "0" to backup image.

from mysql-backup.

Are you using an out of date version? This all was moved over to databack/mysql-backup a while back, yet your compose file references deitch/mysql-backup. Try that. If it doesn't work, turn on DEBUG mode and paste the output (or, if too big, a gist).

To preempt the question, I have wanted docker hub to have a "re-parent" (i.e. redirect) for a long time. It is my hope that I will get it at some point...

Thanks for the quick reply. Moving to the newest release resolved it in that way that the databases are now backuped anyway even if the error messages are still thrown.

from mysql-backup.