Antibios

Mine were updated this morning and checked after

Ran that script and found all my binhex containers on 5.6.1 binhex-jellyfin binhex-delugevpn binhex-sonarr binhex-radarr binhex-hexchat

Thank you so much. This is exactly what I was looking for Tried to buy ya a beer but that link doesn't work anymore

Same here

Is there any way to set this up to run multiple encodes at once? Do I just make duplicate flows?

Thank you, working perfectly now.

This is great and works better than expected. It's not using my nvidia card at all though. I was assuming it would use nvenc/gpu to do the heavy lifting. Do I need to add anything in the docker config? Edit: I added --runtime=nvidia to the extra parameters but I se no field for the UUID to go into

At least on my system, the correct path is /root/.config/neofetch Really cool though I like all the added info Edit: Nevermind, both pathings work

Just to be sure I did a full wipe and re-install with no joy.

Since the latest update I am getting this: 2021-12-13 11:02:44,560 DEBG 'start' stderr output: tint2: xRandr: Found crtc's: 1 tint2: xRandr: Linking output VNC-0 with crtc 2021-12-13 11:02:44,560 DEBG 'start' stderr output: 0, resolution 1024x768, DPI 96 tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'. tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc tint2: Could not read config file. 2021-12-13 11:02:44,560 DEBG 'start' stdout output: Usage: tint2 [OPTION...] I opened console for the container and the entire path after /.config is gone

I tried putting -2.0.4.dev38+g23a48dd01-3-01 at the end of the "repository" field and the "docker" field but it wont pull at all if I do that.

Is it possible to roll back the docker image install on my setup? I tried removing the current install and re-installing a different docker from another repo and the whitelist message is still happening but I'm betting they're in the same downstream

Suddenly my client is reporting wrong info to my trackers and getting me blacklisted. They all support deluge 2.0.X so it is reporting something else after the last update. Any help is appreciated