I've successfully gotten PieFed up and running in its docker iteration and with help from folks here, I'm now backing things up as they should be! I noticed that cron is reporting an error in one of the scripts that is being called though, here is an example of the e-mail that I am receiving:
Subject: Cron phoenix@phoenix docker exec piefed_app1 bash -c "cd /app && ./send_queue.sh"
./send_queue.sh: line 3: venv/bin/activate: No such file or directory
[2026-01-26 03:25:03,595] INFO in init: Started!
I've checked the contents of the script and the line in question appears to be trying to activate a Python virtual environment inside the /app directory, but it appears that this is failing? I'm not sure if that means the entire script is failing as well, but it's certainly generating a lot of e-mails! Unfortunately the Docker image doesn't include an editor of any kind, so I was unable to change the contents of the script, or to install an editor or virtualenv. I'm not sure how to proceed!
Yep that error is harmless. Do whatever is suitable for your system to disable the error reports. Maybe add > /dev/null on the end of each line in the cron file?