Vyressi

There was a bug recently in unraid's docker that made containers regularly report "unavailable" and be unable to update automatically, but still able to update manually. It's been resolved as far as I know in the latest version, but versions that came before that needed a patch plugin from the community store to rpevent this. Regardless when the issue is corrected, you still need to manually update all of the affected containers before automatic can work again.

What are the GID and PID both container is running under?

I've taken the liberty of creating a PR to fix this upstream, waiting on project owner to approve it.

change the docker repository for your container from f0rc3/barcodebuddy-docker:latest to f0rc3/barcodebuddy:latest

I had the issue and this command was able to resolve it cleanly, though it took several seconds for the UI to realize that the service was working. I do get a DNS error on the plugins settings panel of the app though, even though it resolves just fine. My servers also says that I have been online for 21 days, even though it's been in an error status for longer than that, and I just fixed it now. Using the diagnostics command from GUI creates a hung window Using the diagnostics command from terminal creates a hung terminal /usr/local/emhttp/plugins/dyanmix/scripts/# php -f diagnostics generated a logfile, which is attached. tower-diagnostics-20220731-1959.zip

So in order to get this to work I needed to: manually change the permissions on /mnt/user/appdata/TubeArchivist/es to get elastisearch to properly load Changing the permissions wasn't enough so I also needed to add PID and GID environment variables to the elastisearch container. install their version of redis as it would not connect my already installed and functioning version of redis add a TA_HOST environment variable to the main archive, which I only discovered I needed to do after manually probing the log files from the terminal, as the log would close instantly from the unraid docker interface Container loaded fine, and would not let me log in manually specify a non-default TA_USER and TA_PASSWORD, still wouldn't let me log in. go into the container terminal once it stopped closing immediately and hunt down a python script in /app called manage.py execute python manage.py createsuperuser python manage.py drf_create_token %myusername% finally able to log in. Several of these things are because the compose that's rolled into the CA repository is either missing documentation, missing variables, missing options, or does not handle bad startups gracefully.

Running this on br0 I had no local connectivity to the server until I also opened added an allocation to port 137, and I also had no 'server is online' status on the multiplayer screen.

I experience this too, but only on very large containers like Home Assistant. It may be a side effect of the browser tab losing focus, because I never sit there and actually watch the entire thing go through.

Aside from the post you replied to, and my google search to try to find out how to do this that found your unhelpful comment. It's not a big ask to get CUPS on unraid, I have a laserjet 3 that will outlive my grandchildren and can be refilled for pennies on the dollar and eliminating a network drop to the jetdirect server would be optimal.