absent

@Pandora09 I'm not sure you understood this request, S3 is a kind of storage API, its named after "Simple Storage Service" (S3) by Amazon which originally created it. This is a file sharing API/Format not a power thing...

I, likely like many have ended up running a service like MinIO in order to achieve S3-compatible storage. One of the compelling features of TrueNAS is that it has this functionality out of the box, and alongside others like FTP, NFS, etc ref: https://www.truenas.com/docs/core/coretutorials/services/configurings3/ Would be lovely to have something like this directly implemented in Unraid also.

I've been fumbling around at this for a while and I will say to make sure when trying to set this up you do not have "Docker LOG rotation" enabled in the Unraid Docker settings. The issue is that when you add this config docker has `log-opts` passed in as both flags (at runtime by the docker service `/etc/rc.d/rc.docker`) and in the file you've updated. The error you are showing is that the docker daemon failed to start and as a result the UI wont work.

So, I recently upgraded my server and seemed to have put my foot in it by choosing 11th gen (11500) as no suggestions here for the likes of 10th gen will get QuickSync working… Has anyone had any luck getting this transcoding with these Rocket Lake based UHD 750 iGPU chips yet? I’ve experienced it easily doing 6 x 4K > 1080p 10m streams in Plex so know it’s got grunt, so I’m apprehensive to buy a discrete GPU (like a now inferior p2000/2200) for transcoding! Or having to cough up a lot more for an RTX (A)4000 where QuickSync will probably work eventually… One thing about Tdarr is the lack of documentation is next level, if you’re not a developer I really struggle to know how you’d set it up and use it. Concept is amazing though!

@bonienl forgive my ignorance but how do we get access to the updates? Or do we need to wait on the next minor release?

I requested something similar a little while back... My solution died with the 6.8.x update so I have a not-so-great solution not using `binhex/arch-qbittorrentvpn` and luckily jackett supports proxy so using the in-built `Privoxy`, its not a solution I'm fond of, at least my old one I just turned off auto-update on the vpn container and updated it manually if it ever needed it...

Would be great to be able to specify a different docker container for the "Network Type" natively, where a docker container is using: --cap-add=NET_ADMIN --device /dev/net/tun A use case for this is as follows: I have a VPN Client Docker (dperson/openvpn-client) [called "vpn"] that's permanently connected to my VPN provider (PIA in my case) I then have 2 dockers which tunnel their network through that container (jackett and qbittorrent) At present I have come up with a bit of a hack after lots of messing around where I set the 2 dependent containers Network Types to "None", then add into "Extra Parameters": --net=container:vpn Hopefully this could include a UI update that would use the containers name instead of the UID too I know what I have done is probably massively hacky, but I couldn't get it to work how I desired any other way. I did not want the VPN at the server level, as that interferes with things like Plex remove services, etc. And hey, I'm a developer; sometimes the solution is just "I need to get this to work, It don't need to be pretty".