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!

  • wjs018@piefed.socialEnglish
    2·
    2 days ago

    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
    • Phoenix1@piefed.socialOPEnglish
      1·
      2 days ago

      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!