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:

  1. The podman install is fucked somehow
  2. The drive itself is fucked
  3. 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!

all 4 comments

sorted by: hot top controversial new old
[–] 3 points 1 year ago (1 child)

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...

  • source
  • hideshow 1 child comment
  • This may be helpful: https://www.tutorialworks.com/podman-rootless-volumes/#how-to-allow-a-rootless-podman-container-to-write-to-a-volume

    The real trick is set the ":Z" flag for the volume. This usually solves most problems, but will not allow that same volume to be used with other running containers.

  • source
  • [–] 2 points 1 year ago* (last edited 1 year ago)

    Out of curiosity, are the containers that are having issues using non-root users internally? Podman maps your user to root inside the container, so a non-root user can have strange effects.

    I had this issue when an image inherited a non-root user upstream.

  • source