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!

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 1 point 9 months ago

Very good to know that it's not harmful at least, I figured if the scripts did not contain set -e, then they probably just proceeded onto the next line and ran successfully, but I thought it better to check with the experts 😁 Great idea about the cron file though, I will try that and see if it accomplishes the same effect as modifying the scripts does! Modifying the cron file would of course be more convenient...

Is it possible that the scripts could be updated in a future version to avoid the error being thrown, perhaps? Thanks so much!

  • source
  • parent