CODEWITHSUNDEEP
mysqllinuxdockercron
Niiskandar Nideha
Niiskandar Nideha

Reputation: 21

docker exec and mysqldump in cronjob problem

I found some problem when I used docker exec and mysqldump in cronjob

I wanted to backup my database in container and tried this and it worked well

sudo docker exec -it --user root lemp_mariadb mysqldump -uroot -pxxxxxxx iot  >/home/backup/backup_data.gz

But when I used this in crontab I got file output without anything and the file size is 0 byte

0 24 * * * docker exec -it --user root lemp_mariadb mysqldump -uroot -pxxxxxxx iot >/home/backup/backup_data.gz

What did I do wrong?

Upvotes: 2

Views: 1844

Answers (2)

abetobing
abetobing

Reputation: 191

Jason Peacock answer is right But i would prefer to move the dump command into another shell script:

vim /home/backup/backup.sh

inside the backup.sh:

#!/bin/bash
echo 'Backing up db'
docker exec --user root lemp_mariadb /usr/bin/mysqldump -uroot -pxxxxxxx iot | gzip -9  > /home/backup/backup_data.sql.gz

chmod a+x /home/backup/backup.sh

Then in your crontab:

0 24 * * * /home/backup/backup.sh

Upvotes: 4

Jason Peacock
Jason Peacock

Reputation: 1831

When you run the command manually, you are including sudo, but when you run the command in the crontab, you are not. Unless you are installing this as the root crontab, it will fail.

See the Manager Docker as a non-root user instructions here about how to setup Docker to run as non-root user.

Also, you are using the -it options, which expect an interactive terminal that is not available when run from crontab. You need to remove those arguments.

To get more details about the failure, you can redirect errors from the crontab command to a file for examination with 2>/path/to/file.

Putting it all together, your crontab entry will look something like:

0 24 * * * docker exec --user root lemp_mariadb mysqldump -uroot -pxxxxxxx iot  >/home/backup/backup_data.gz 2>/var/tmp/docker_msqldump_errors.log

Upvotes: 5

Related Questions