this post was submitted on 22 Oct 2024
7 points (100.0% liked)

linux4noobs

1378 readers
1 users here now

linux4noobs


Noob Friendly, Expert Enabling

Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.


Seeking Support?

Community Rules

founded 1 year ago
MODERATORS
 

I've been migrating to linux recently and next headache on the list are my starr apps (sonarr, radarr, etc). On windows I just had them installed as background services but I wanted to give (rootless) podman a try on linux since everyone kept recommending it and saying how much better the experience is than on windows.

Anyway, I've set everything up and some of the services work, but specifically sonarr and radarr can't write to the main media folder with the error: Folder '/data/media/tv/' is not writable by user 'abc'

So, first of all, I didn't make user 'abc', it is some internal docker/podman/starr user allegedly and it's supposed to be mapped to my real user, which I did by providing the PUID=1000, PGID=1000 env variables.

Second, I tried to give read and write permissions to everyone for the placeholder folders but it didn't change anything. I don't think this is the issue since other services like the one for sabnzbd or jellyfin had no problems using folders I created.

Googling for the issue brought up some topics about NFS shares but I don't know anything about this - this is not a NAS or even some external drive, it's just podman installed on fedora.

Any help is appreciated, here's a pastebin of my compose file if it's relevant https://pastebin.com/uX9Saqvj

top 2 comments
sorted by: hot top controversial new old
[โ€“] [email protected] 2 points 4 weeks ago (1 children)

With rootless podman, the internal PUID/PGID being set to 1000 within the container is likely being remapped into your subuid/subgid range (eg, if your /etc/subuid is cyno:100000:65536, id 1000 within the container becomes id 101000 outside of it). You can use podman's --userns=keep-id parameter to map your own host uid 1000 to id 1000 within the container.

[โ€“] Cyno 1 points 4 weeks ago

Thanks for the suggestion! I'm struggling a bit to incorporate that command into podman compose though, I'm reading through this issue and I'm a bit lost.

Do I just add this to sonarr section in my yaml? I tried it and it doesn't seem to have done much

x-podman:
    keep-id:uid=1000

Should I try and switch everything to podman kube play as some user there recommended maybe?