71
submitted 11 months ago by anzo@programming.dev to c/selfhosted@lemmy.world

It has an 'App store' that's been growing a lot lately. Writing new docker-compose.yaml files is easy (see: https://www.runtipi.io/docs/contributing/adding-a-new-app ), and exposing them behind NAT, e.g. from home it's easy too (see: https://www.runtipi.io/docs/guides/expose-apps-with-cloudflare-tunnels )... But my favorite perk is the folder structure (see: https://www.runtipi.io/docs/reference/folder-structure ), and the fact that 'media' is shared between apps.

you are viewing a single comment's thread
view the rest of the comments
[-] Luckaneer@lemmy.dbzer0.com 1 points 10 months ago

PID/GID 1000

Can I pick your brain on this? I have my folders set to 1000:1000 , Radarr can import the movies folder but Sonarr complains about the tv folder not being writeable by user abc.

The tv folder looks to have the same permissions to me though? Any idea what could be up with that?

[-] anzo@programming.dev 1 points 10 months ago

To be clear, you have a (user:group) 1000:1000 on both containers? What about having the same mapping of Uid and Gid on the host? I assume the host is a desktop distro, and they usually have it already. You would require the three, so that permissions are "coherent" between each system

[-] Luckaneer@lemmy.dbzer0.com 1 points 10 months ago

Yeah the user:group mapping was correct. I did work it out though. It was the storage volume being full, it presented as not being writeable! My mergerfs config wasn't quite right. As soon as I set it to most free space it was working again.

It's just funny that I didn't get the same error in Radar.

this post was submitted on 07 Aug 2023
71 points (96.1% liked)

Selfhosted

37824 readers
396 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS