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!

From what I can tell, inside the Docker image, there is no Python virtual environment, so the script generates an error when it tries to activate one. Unfortunately there are several scripts that try to activate a virtual environment inside Docker, so there are a ton of these e-mails being generated. I guess it would be necessary to patch the line out of each script somehow, but how would one do that without access to a text editor?

Yeah...I can see why this is annoying if you have things set up to send an email every time the scripts run. Failing to activate the venv in docker is actually expected since there isn't a venv, it just runs baremetal from the container's POV. That line is necessary only for baremetal installs. The rest of the script still executes just fine even with that error.

We can take a look at trying to prevent this erroneous error from being thrown in a docker environment. In the meantime, the files you would need to comment out that line would be:

• daily.sh
• remove_orphan_files.sh
• email_notifs.sh
• send_queue.sh

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?

Thanks very much for the list of files that need to be modified, that makes it much more simple at least. It's possible to write out a text file with cat, in the event that an editor is not available, but it's not the most convenient thing. It works though!

If it would be possible for the developers to edit the scripts so that manually applying the fix is no longer possible in the future, that would be wonderful, but for now the error is gone at least!

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!