

@mjr I think, you are writing about Owncloud.
Opencloud is newly written with Go, so it can’t be a fork of PHP driven Owncloud or Nextcloud.
SELECT
‘#bicycle 🚴♂️’
,‘#databases’
,‘#sql’
,‘#selfhosting’
,‘#Linux 🐧’
,‘Team vi’
,‘#mdRzA’
,‘Generation X’
FROM life
WHERE 0 = 0
;


@mjr I think, you are writing about Owncloud.
Opencloud is newly written with Go, so it can’t be a fork of PHP driven Owncloud or Nextcloud.


Probably https://opencloud.eu/ could be an alternative.


@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 \_data


@theorangeninja Did you have tried a ls -al on 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/


@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 --userns for 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.
@Nighed Sorry, but I currently don’t use Opencloud and I don’t have insights in the code.
But maybe the code itself has an answer for your question.
https://github.com/opencloud-eu