Bazarr starting but not reachable

[iluapot]

Hi,
I have Docker running on Synology DS920+ (DSM 7.2 Update 4) and using Bazarr container managed in Portainer (not Synology Container Manager). I realized I cannot upgrade to any version above v1.5.2-ls309 because, if I do, the container is not reachable. I have tried using IP_address:port as well as reverse proxy but it does not load.
When I start the container using v1.5.2-ls310, or latest or 1.5.3 it seems it starts up but the only entries I see in the log is:

/run/s6/basedir/scripts/rc.init: line 35: /init-hook: not found
/run/s6/basedir/scripts/rc.init: fatal: hook /init-hook exited 127
s6-linux-init-hpr: fatal: unable to talk to shutdownd: Operation not permitted

I made sure I am using PUID and PGID for the specific docker user.
Any ideas?

[drizuid]

A few things to start

1. we do not support deploying containers with portainer, it is known to cause numerous issues (we also do not support deploying with synology's docker ui)
2. usually we would need your compose, but with portainer in the picture it's a bit difficult
3. i suspect the issue you're running into is that synology has a kernel that has been end of life for years and the docker version has also been end of life for years.

We are willing to try to help, but your best bet is to come on discord and provide screenshots of your setup and we will provide best-effort help for this unsupported setup

[iluapot]

Thanks for the answers, I was not aware I was using an unsupported environment, point taken. I'm a bit surprised though that a minor update (1.5.2-ls310) could break the instance, I cannot see any information about major changes that could cause this issue.
I really appreciate you suggestion, I'll use Discord to try and get the issue sorted.

[drizuid]

to be clear, it SHOULDN'T have broken anything, ls309 to 310 was very minor updates in the OS base layer
specifically, anstream, libexpat, lxml, and rav1e-libs all receiving VERY minor subversion updates

the issue is that your environment makes it very difficult for us to reproduce things... we do have users with synology units, but none would use portainer or container manager, they would just use docker compose

[iluapot]

I understand, I have also reviewed the Support policy and it makes sense what you are saying. However, I am pretty sure there must be users out there using your images in Synology via Portainer, maybe none in Discord or active here.
I'll try my luck in Discord as recommended, many thanks.

[drizuid]

However, I am pretty sure there must be users out there using your images in Synology via Portainer, maybe none in Discord or active here.

There are for sure and it CAN work, it's just not something we will spend a lot of cycles on because of all the known issues. Similarly people use container manager without issue, but we still won't support it officially.