Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
@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?