Technology

59217 readers

3089 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

441

Here comes another Netflix price hike (www.theverge.com)

submitted 1 year ago by [email protected] to c/[email protected]

101 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago (3 children)

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.

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.

[–] [email protected] 1 points 1 year ago

Just in case this helps, I think nearly all the docker containers in Unraid have these settings set: https://snipboard.io/D6ZagQ.jpg

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

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

[–] [email protected] 1 points 1 year ago

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 777 everything