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 :)

I can tell you from my own experience, you don’t do the child a favor by sticking to a broken relationship, I wished my parents have broken up earlier instead of pretending everything is good and that’s how a normal relationship should be. It took me years and I sometimes still struggle today to draw a line and go into a conflict with my partner to figure things out instead of avoiding the conflict

It is, from it’s current animals in London series. Talented person 👌

Who could have guessed??? Anyway it’s important to think about the economy now, but only short term of course! /s

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

The best patriots are those, that are willing to sell their country to China/Russia! Heck yeah, love it! (Fucking dumbasses)

Always surprising for how less money these “patriots” are always willing to sell their country to dictators. Sure 20k is money, but it is at max 3 of his monthly paychecks as a member of the Bundestag.

I still prefer it, HDDs aren’t free and I personally really can’t tell the difference (my TV kinda sucks anyway)

Your old stuff is most likely in x264 video codec, while, especially at the higher resolutions, x265 / HEVC and in rare cases AV1 are the standard today. But it also depends on the specific release how many streams (like audio tracks, subtitles) are included

For the remote management, either a VPN to your parents network or exposing (e.g. Cloudflare Tunnel)

And that’s the job of the government, imo. Regulate the shit out of the free market, force the manufacturers to not use the worst things possible

Uhm yes? You bought it, it’s yours. You made the decision to buy something that contains plastic or is wrapped in it or whatever, that’s where the responsibility went to you.

They have to find someone else to do their job now

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