Rank 1: Thread
yes, exist
Votes
2
Replies
24
Participants
Unknown
Messages
25
Rank 1: Thread
yes, exist
OK, sorry I've made a mistake
Try this
#!/bin/shcd /home/ubuntu/appwrite
mkdir -p backup
/usr/local/bin/docker-compose -f /home/ubuntu/appwrite/docker-compose.yml exec mariadb sh -c 'exec mysqldump --all-databases --add-drop-database -u"$MYSQL_USER" -p"$MYSQL_PASSWORD"' > ./backup/dump.sql
appwrite_volumes=(uploads cache config certificates functions)for volume in ${appwrite_volumes[@]}; do mkdir -p backup && docker run --rm --volumes-from "$(docker-compose ps -q appwrite)" -v $PWD/backup:/backup ubuntu bash -c "cd /storage/$volume && tar cvf /backup/$volume.tar ."doneRank 1: Thread
I continue with the problem. Thank you so much for your time and effort!
did you get it working?
Rank 1: Thread
Not yet 🥲
weird...so btw, you shouldn't need to run sudo with docker. you may have missed a post installation step: https://docs.docker.com/engine/install/linux-postinstall/
i tested by adding a cron job for my user (rather than root). the cron job had:
*/5 * * * * cd [path to appwrite folder] && ./backup.sh
I used the original backup.sh script.
I wonder if you have a problem with docker compose for your root account
Rank 1: Thread
everything happens normally when I run the backup.sh script directly in cmd
Rank 1: Thread
Files are generated
Yes of course. The problem is with cron path
perhaps it would be good to try and get some output. try to update your crontab command to:
cd /home/ubuntu/appwrite && ./backup.sh > /tmp/cron-backup.log 2>&1
Rank 1: Thread
././app-63ab55ce4321283aa7fe/./app-63ab55ce4321283aa7fe/63c9aa8377f9fb2109d7/```Rank 1: Thread
I get this error: the input device is not a TTY
Rank 1: Thread
the rest is basically the same as normal operation
Interesting that it doesn't work for you though...
You can try adding -T flag to the docker compose command
Rank 1: Thread
I no longer get the TTY error and the file is still empty
How did you install docker?
Can you test docker compose version in the script? You can probably comment out everything else while we troubleshoot the docker compose problem
Rank 1: Thread
Rank 1: Thread
like this link
this is an old docker compose 👀 you need docker compose v2
you should definitely try and uninstall that old compose. maybe it was installed via pip?
Rank 1: Thread
@Drake @Binyamin after updating everything, docker and docker-compose the problem was solved. I really appreciate your help!
Rank 1: Thread
[SOLVED] Cron for backup 💾
Rank 3: Container
checking
Please don't post in an old thread like this. If you need help, create a new post