I do not use synology or portainer. I like the control of spinning up my stacks manually from the command line using compose files.
After verifying I was getting a different python path than you, but that /lsiopy/bin was in my path, I brought down my container, and ran
docker system prune -a
I spun up my container again, and ran the commands you gave me:
>>> $ docker exec duplicati which python3
/lsiopy/bin/python3
>>> $ docker exec duplicati bash -c 'echo $PATH'
/lsiopy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Rebuilding my container seems to have fixed the problem. I am getting a new error, I believe is related to needing the docker.sock configured, but that is not related to this topic.
Thank you for your help, @aptalca ! You gave me some troubleshooting steps I can use in the future.
When in doubt… docker system prune -a