Comment on [beta] degoog - search engine aggregator
thestrike@lemmy.blahaj.zone 5 days agoI had the same problem so let me know if you find a solution! I just switched to running as root with podman
Comment on [beta] degoog - search engine aggregator
thestrike@lemmy.blahaj.zone 5 days agoI had the same problem so let me know if you find a solution! I just switched to running as root with podman
KarnaSubarna@lemmy.ml 4 days ago
Note that I’m running it on a rootless docker instance, and NOT on Podman. So, the following solution might or might not work for you.
Explanation: rootless docker works a bit different from rootful docker. user 1000 (which is you on your server/machine) will be mapped to a different UID (e.g. 32555). This is to ensure that any process in docker container can’t have access to folders/files that you have access to, in case it manages to break free of docker containerization.
When you put user: “0:0” in a rootless docker container, it will assume your UID 1000 (which is you on your server/machine) inside docker container.
While it solves the file permission issue, but it is NOT a recommended way.
with user:1000:1000
Image
with user:0:0
Image
thestrike@lemmy.blahaj.zone 3 days ago
Is there a recommended way to do it? Could I give file permissions to the UID that docker has or something? Or put docker in the same user group as me