- cross-posted to:
- technology@lemmit.online
- technews@radiation.party
- cross-posted to:
- technology@lemmit.online
- technews@radiation.party
Get ready to pay more for Netflix’s priciest plan.
Subscribers to Netflix’s Basic and Premium plans will be paying more, with prices rising to $11.99 and $22.99 per month in the US.
I’ve been doodling around with Plex and sonarr in a Docker setup on my Linux box, but I’ve run into some issues that I can’t figure out. Any good resources to recommend for creating the optimal setup?
I can’t say I know of a good single resource, I’ve learned a lot about docker and linux over the years just googling and trying things. There are now a number of scripts and docker-compose setups that will get everything set up for you with little effort.
My setup is using docker containers running on the UnRaid OS. UnRaid makes docker deployment slightly easier, but it requires that a docker container also include a custom config file that allows it to be configured via unraid’s webui. I’ve found this limiting from time to time, when I find dockers that I want to use, but couldn’t install via the webui. So I learned a bit about using docker from the command line, which actually wasn’t all that hard. Especially with docker-compose.
One issue in particular that took a minute to figure out with docker, if you need the containers to talk to eachother, you have to be aware that certain types of docker network connections will not automatically see the other containers, even if both containers are connected to your home network.
Just stick with Plex/Jellyfin + any and all apps ending with *arr (aka the *arr stack).
Yup, this is exactly the issue I haven’t been able to figure out. For some reason, the files I download in Sonarr are associated with a user group that Plex isn’t a part of, so Plex can’t see the files (and I’ve tried adding Plex to that group and it still doesn’t work, argh). I know you can specify a UID and other specifics when you initialize a container, but inside the container itself that doesn’t seem to apply, it sets its own user parameters. I’m about ready to throw in the towel and just run the software on my machine itself with a VPN, because then at least everything will be able to talk to each other.
Luckily perms don’t seem to be much of an issue on UnRaid, I think there’s a solid convention for user and group so files are generally accessible to all apps.
Worst case scenario, you just
chmod 777everythingJust in case this helps, I think nearly all the docker containers in Unraid have these settings set: https://snipboard.io/D6ZagQ.jpg
Make a new user group and add everyone to it, then change the permissions of the target directory Sudo addgroup newgroup Sudo usermod —append —groups newgroup user Sudo chown -r newgroup:newgroup ./*
I had the same issue. Adding it all to the same group fixed it for me