It totally depends on how you expose it to the outside world. If it’s exposed just like it is, it works fine with every device. If you put an authentication before it (e.g. Authelia), it can only be accessed by browsers from outside the network. That being said, it’s not recommended to expose Jellyfin directly, because there are a ton of security flaws. Best practice is to use a VPN

renderD128 (Intel dgpu) couldn’t be added to the container (linuxserver image). Will take a look later, when I’m home, to find the issue. But may take your time for the update and don’t yolo it like I did :)

You could try using bindfs to spoof the original user id and then chown the whole drive after successfull mounting (i’m a noob, just my understanding of the issue, don’t know if that’s really possible)

This feels more like a shitpost than a guide

The good thing about Linux is, it’s not very ressouce demanding. If you pick the xfce version of Mint, you can get away with 4GB of RAM. But you won’t have that much fun coding as soon as you start something more ressource heavy (big data sets, ML, …) so this depends a little in which direction you want to go. However see if you can find something used, preferably something you can open from the back side to upgrade components like SSD and RAM (cheaper than buying higher specs)

Sorry, I meant risk taking not averse (not my 1st language) Regarding the bugs, they get usually fixed within days

*10.9 if not latest. For the risk averse folks out there, check out https://github.com/containrrr/watchtower I just let it run every night, so far w/o problems

Since you already got a lot of ELI5s, here is a basic to-do to get you up and running. From my experience, since I use the exact same setup as you describe.

1. Set up your containers in a way you can reach them from you local network (e.g. http://123.456.789.10:123)
2. Get a domain name (you can get one at the registrar of your choice, e.g. mydomain.com)
3. Set up NGINX proxy manager (NPM) (default address of webui would be http://123.456.789.10:81)
4. Set up a new proxy host in NPM:
   • Domain name: mycontainer.mydomain.com
   • Scheme: http
   • Forward Hostname/IP: 123.456.789.10 (if you get an error later on, you can use the docker container name if NPM and your container are connected to the same Docker network)
   • Port: 123
   • Via access lists you can provide a very basic username/pw login to protect your sites (you can do more and cooler stuff with Authelia)
   • In the SSL tab you can (and should) setup the SSL encryption: https://www.youtube.com/watch?v=TBGOJA27m_0
5. Go to the DNS management of your registrar
   • Add an A-record for mydomain.com and the public IP of your server (you can google public IP to find it out)
   • Add a CNAME record for the subdomain with name mycontainer and target mydomain.com
6. open port 443 of your server in your router If everything worked right, you can visit mycontainer.mydomain.com, your DNS server will resolve this to your public IP and forwards the request to nginx, which will serve the data of your local container