permission error when using backups.py

[wisgit]

I tried backups.py for backing up the postgresql db of TandoorRecipes (Thanks to vabene1111 for providing all this to the community!).
However, I failed to restore a dump file with the command "python backups.py -l <my_config_profile>". It ended with the error message "PermissionError: [Errno 13] Permission denied: '/home/pi/tandoor/postgresql/'", which resulted from the call "shutil.rmtree(pg_data_dir, ignore_errors=False, onerror=None)" within backups.py.

I know that my dump file (and all entries in the config.ini) were OK, since I was able to restore the dump file (successfully created by "python backups.py -d <my_config_profile>" manually with the command sequence:

• docker compose stop db_recipes
• sudo rm -r /home/pi/tandoor/postgresql
• docker compose up -d db_recipes
• (wait for >2 sec)
• docker compose exec -T db_recipes psql -U djangouser postgres < /home/pi/tandoor/dumps/.sql

I found later that I could delete the postgresql folder using 'sudo python' and then using the shutil.rmtree() routine in the interactive python mode. But when starting the script backups.py with "sudo python backups.py -l <my_config_profile>", I receive the error message "docker: 'compose' is not a docker command."

Some further remarks:
I had installed docker (in rootless mode) on a raspi 3B+ (headless, bullseye) in folder /home/pi/tandoor, where I then installed the TandoorRecipes App (following an article in a recent issue of ct magazine).
The dump part of backups.py I had to modify before it worked: I had to replace all occurences of "/usr/local/bin/docker-compose" with just "docker compose" (Note the missing '-').

[dr-froehlich]

dito for me... I have spent 3h trying to get a working backup solutions for the tandoor recipe database.

It's actually obvious, but it took me a little to figure out what needs to go into the config.ini:

# Name of the postgres docker container
pg_docker_container: db_recipes
# Username to use when dumping data
pg_docker_user: djangouser

I used the same raspi installation. I ran into the "docker-compose" vs. "docker compose" issue (which I understand is v2). Instead of changing the script I tried to install "compose-switch" and failed as the binary is only for arm64 and not armv71. Luckily I found your, @wisgit, note and changed the script.

When I run "python3 backups.py -d" I get a "dump.sql" file in my postgresql folder. The folder is owned by root with excluisve rx rights. I added a group and group rx rights for my own user. However, also the "dump.sql" file is owned by root and cannot be moved by the script, nor can I run the backup script as root as "docker compose" doesn't like to be run as root (using sudo):

python3 backups.py -d -v
Loading Config:default
Creating DB dump ...
starting container: /usr/bin/docker compose up -d db_recipes
unknown shorthand flag: 'd' in -d

@vabene1111 : Tandoor recipes is terrific, but at this point it, while it was straight forward to set up Tanndoor (with the help of the mentioned c't article), my capabilities and endurance run out getting a stable backup / restore solution to work. I don't trust my pi and setup enough to spend hours entering recipes and not have a bulletproof solution to backup the data for good.

I support https://github.com/TandoorRecipes/recipes/issues/79 , but in the meantime any help or instructions on getting the job done with this script would be very helpful -thanks a million!

How I installed docker:

'curl -fsSL https://get.docker.com -o get-docker.sh'
'sudo sh get-docker.sh'
'sudo usermod -aG docker $USER'

[wisgit]

@dr-froehlich wrote;

It's actually obvious, but it took me a little to figure out what needs to go into the config.ini:

# Name of the postgres docker container
pg_docker_container: db_recipes
# Username to use when dumping data
pg_docker_user: djangouser

When I run "python3 backups.py -d" I get a "dump.sql" file in my postgresql folder.

You should also have something like the following in the relevant section of your config.ini
# Absolute path to directory to store backups in
storage_dir: /home/pi/tandoor/dumps
(in my case it's "/home/pi/tandoor/dumps" where my dumps are stored. I had created folder "dumps" manually and it is owned by pi:pi, permissions are oktal 755)

My temporary workaround is (i) backing up with
python backups.py -d [name of relevant config.ini section]

and (ii) restoring manually with

docker compose stop db_recipes
sudo rm -r /home/pi/tandoor/postgresql
docker compose up -d db_recipes

(wait for > 2 sec )
docker compose exec -T db_recipes psql -U djangouser postgres < /home/pi/tandoor/dumps/<dumpfile>.sql

where of course is the dump you want to restore. All of this should probably go into a bash script (but I haven't yet found the time for it)

[vabene1111]

honestly this repo just exists because i still run my backups using it on some of my servers, i have not really spend time working on it, testing it and really building it out. I have since found a nice tool that simply works a little better than mine so i am using this one now https://github.com/prodrigestivill/docker-postgres-backup-local

I will update the warning in the readme again