Hello everyone,
I am currently trying to transition from docker-compose to podman-compose before trying out podman quadlets eventually. The first couple containers work great but today I tried Linkding and I run into a weird error.
Linkding can’t access the data directory because the permission gets denied. After inspecting the container all the directories inside belong to root. But podman runs rootless so that must be the issues. I tried to change the owner of the data directory on the host to root but then the data directory in the container belongs to nobody and nogroup (?). After checking the environment variable documentation of Linkding it seems like there is no environment variable for a UID and GID.
I think I have a fundamental misunderstanding how rootfull and rootless containers work so I would be very grateful if anybody could point me in the right direction on where to get a solution for this problem or anybody had success running Linkding rootless.
Thanks a lot in advance!
Edit:
I used named volumes because that’s what the dev used in the example compose file. Now I tried to use named volumes instead and now everything seems to work fine. No error in the logs and the web ui is accessible.
@theorangeninja Rootless podman container and owner of created files - always a mystery.
Maybe, the part belonging to “Using volumes” could help:
https://github.com/containers/podman/blob/main/docs/tutorials/rootless/_tutorial.md
If the container process is running with another UID than 0 (root), created files on the host belongs to another UID, calculated based on settings from
/etc/suduid.You should have a look into
--usernsfor mapping of UIDs between container and host:https://docs.podman.io/en/latest/markdown/podman-run.1.html
For PostgreSQL I’m using
keep-id:uid=999,gid=999.I went on and tried something else and when using named volumes (the dev uses bind mounts in his compose file) everything works without errors.
@theorangeninja Did you have tried a
ls -alon the used volume?The podman volume path can be found here:
`podman info --format ‘{{.Store.VolumePath}}’``
When you use $HOME/linkding as volume mount and the linkding container process is running with <> UID 0, then the created files are belonging to another UID than your UID.
Maybe this tutorial explains it better:
https://www.tutorialworks.com/podman-rootless-volumes/
I checked the tutorial and setting the private label
:Zworked when using $HOME/… as bind mount. For named volumes from podman itself that was not necessary, it worked out of the box.Like I said the dev used bind mounts so I sticked with that but he was probably using docker so he didn’t have this problem.
@theorangeninja I would suggest again, that you try to access the content of the podman volume as host user, which is running the podman container.
I think, that it would looks like this and that you can only access it using
podman unshare:drwxr-xr-x 1 166446 166446 66 28. Jul 20:43 \_dataWhen I run the compose file with bind mount
./dataand no :Z label I get these results:ls -layields the currently logged in user as owner of the data directory.podman unshare ls -layields root as owner of the data directory.So do you think this is the basis of the problem?