Closed T81 closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
I suspect you're experiencing the same as portainer and Synology GUI's: https://info.linuxserver.io/issues/2023-05-22-portainer/
Most likely this https://info.linuxserver.io/issues/2023-05-22-portainer/
Everything else, that is, 14 containers are all working fine except when updating bazarr. I am using portainer for management. This has happened when the image rebased to Alpine, maybe this is causing the issue. It looks more than a coincidence
Bazarr has been on a version of our Alpine base image since the container was first published in 2018. The links that have already been posted clearly explain the issue; it doesn't affect all containers and is particularly an issue with Python-based applications.
It's a consequence of lazy design by the Portainer, and other, devs that silently overwrites configuration provided by the image maintainers.
I see. The rebase to Alpine claim is my fault. The last working version is v1.2.4-ls207. After this I get the import error. So using docker compose for example, will solve this issue, right?
That's our recommendation, otherwise you can completely remove it from Portainer and redeploy, rather than doing a recreate/update, which will work around the issue.
Redeploying outside portainer solved the issue
For anyone who wants an actual solution other than unwinding their whole Portainer setup, I had some success with (1) removing/deleting everything Bazarr including the downloaded images, volumes, etc, and (2) taking out the environment variables for PATH, HOME, TERM from my docker-compose stack in Portainer. Redeployed the stack and it works fine for now.
Is there an existing issue for this?
Current Behavior
App does not start due to "ModuleNotFoundError"
Expected Behavior
No response
Steps To Reproduce
Deploy container on a QNAP
Environment
CPU architecture
x86-64
Docker creation
Container logs