Linux

11682 readers

20 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
Be respectful: Treat fellow community members with respect and courtesy.
Quality over quantity: Share informative and thought-provoking content.
No spam or self-promotion: Avoid excessive self-promotion or spamming.
No NSFW adult content
Follow general lemmy guidelines.

founded 2 years ago

MODERATORS

[email protected]

Any help with a permissions issue re: containers? (sh.itjust.works)

submitted 6 days ago by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

So I've been using rootless podman-compose to run my arr stack forever, and I've never had this issue. What seems to be happening is that sometimes, but not always, when a new folder is created or an existing folder's contents are modified, it seems to be setting the files and their folder's owner to "52587" which does not exist. This causes it to then not be able to access those files. I can manually change them back, of course, but the container just overwrites it again. If I specify the user in the compose.yml, it seems to ignore it. It is happening with a few different containers (all in the same compose.yml), as I've seen it now with Radarr and NZBget. The files are on a 12TB drive, and the container mounts and compose.yml are on the same drive, but the OS (Bazzite) is on a separate drive.

My thoughts so far for possibilities:

The podman install is fucked somehow
The drive itself is fucked
Bazzite's weirdness is causing an issue

For #1, podman comes with Bazzite by default so I'm not entirely sure if I can rpm-ostree remove and reinstall, though that might be the next step I try. I'm not terribly good with podman to begin with so I'm not sure how to go about troubleshooting it much otherwise.

For #2, this is entirely a possibility, the drive is pretty old, but I'm not seeing any errors or anything in the SMART stuff and outside of this specific issue I have seen no other problems there.

For #3, this issue did start to happen maybe a month after switching from Arch to Bazzite, mostly because I also wanted to use this machine for Sunshine streaming and my arch install was a mess anyway. I know Arch, though, and this immutable stuff has tripped me up before, so maybe I go back. Feels like admitting defeat though, lol.

Any ideas to point me in the right direction would be greatly appreciated. Thanks!

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

[–] [email protected] 0 points 6 days ago

I only have experience with docker not podman so this may be completely useless, but I found that some containers respect environment variables

environment:
  - PUID=xxx
  - PGID=yyy

and some use the user mapping

user: xxx:yyy

(I guess this needs translating to uidmaps for podman). Maybe this is an issue here? Although #3 makes it sound like maybe not...