Devon Blinston
Devon Blinston
Regardless of whether I use podman or podman-compose it fails with the same error. I ran the compose with debug, extracted the command it had generated and tried running it...
I also tried just calling podman pull against the image and it resulted in the same error.
``` podman@project-hydra:~$ podman unshare cat /proc/self/uid_map 0 1001 1 1 165536 65536 ``` It is as expected. I should also note that it is not a subset of packages like...
Alright, I don't think it has anything to do with my .container file. I am running into the issue with or without that file there.
I'm fairly new to all this stuff, but at the very least I can tell you that a full podman system reset does not reliably fix it. I had to...
@giuseppe dropping the UIDMap does resolve the issue but means that my container is running as the user who started the process, which I do not want. Increasing the range...
Actually, that does not resolve the issue. I tried it again today and regardless if the UIDMap is there or not, it will fail to pull if a different image...
@mikerubicon I validated that that path exists for me, I did find that the volumes were owned by container users 😦 : ``` drwx--x--x 17 podman podman 4096 Dec 27...
Any updates on this? I am still getting this error every time I try to add a new application to my homelab. I just need to know what causes it...