[BUG] Docker not starting after upgrade about docker-bazarr HOT 14 CLOSED

Change the PATH variable to include: /lsiopy/bin:
(So for mine: /lsiopy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin)

Did wonders for me :).

from docker-bazarr.

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

from docker-bazarr.

https://info.linuxserver.io/issues/2023-05-22-portainer/

from docker-bazarr.

Yeah, I found that in a previous report.
But didn't quite get it. But after reading it again for a few times, I think I do.

So I shouldn't create/update the containers through the docker GUI but with command line?
Also if I recreate/update the existing container with command line, will that fix it?

from docker-bazarr.

We recommend compose, but cli would also work. You just need to recreate with the correct parameters (portainer and syno gui inject incorrect params during update)

from docker-bazarr.

Thanks for the info.
You don't happen to have a compose script I can use in the task scheduler?
I think I came across one once when I was looking into docker, but I can't seem to find it again.

Thanks in advance! I'll keep looking tho. :p

from docker-bazarr.

Change the PATH variable to include: /lsiopy/bin: (So for mine: /lsiopy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin)

Did wonders for me :).

This works for me as well.

from docker-bazarr.

This is not a sustainable fix and will just break next time we change anything in the PATH or any other environment variable.

The fundamental issue is with the associated tools botching their management of the containers on an update.

from docker-bazarr.

This is not a sustainable fix and will just break next time we change anything in the PATH or any other environment variable.

The fundamental issue is with the associated tools botching their management of the containers on an update.

Absolutely, but that's not really a fight which the normal user can hold right (I for instance also do not know what's exactly going on. I see a broken container, I try to fix it)? Just for the sake of fixing it so people can move on, I'd say its proper info.

Thanks for providing though, your efforts are tremendously appreciated.

from docker-bazarr.

Well I've made a scheduled task on Synology that I can trigger when I want to update with CLI that stops, removes, updates and creates the container again.
Script is below.

docker stop bazarr
docker rm bazarr
docker pull linuxserver/bazarr
docker run -d --network=bridge -p 6767:6767 -e PUID=xxxx -e PGID=xxx -e TZ=Europe/Brussels --name=bazarr -v /path/to/config:/config -v /path/to/media:/media linuxserver/bazarr

So this issue can be closed. Thanks for nudging me in the correct direction everyone!!! :)

from docker-bazarr.

Fyi, we don't recommend automatic updates and that command you've got in your script, will cause you issues.

from docker-bazarr.

Fyi, we don't recommend automatic updates and that command you've got in your script, will cause you issues.

It's not an automatic update. It doesn't run scheduled. :) Just for me to trigger it when I need it.
And how will this cause issues?

from docker-bazarr.

Well, you've just used our place holder paths and not actually replaced them with your relevant paths. If you want to continue this discussion, jump over to our discord or forum.

from docker-bazarr.

Oh, those paths aren't the ones I'm using. Just as an example. I tested the script and it works. :)

from docker-bazarr.