When I run the compose file with bind mount ./data and no :Z label I get these results:

ls -la yields the currently logged in user as owner of the data directory.

podman unshare ls -la yields root as owner of the data directory.

So do you think this is the basis of the problem?

I checked the tutorial and setting the private label :Z worked 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.

This solved it when using a bind mount! The other option is using named volumes which also works without errors.

On a different note, can I ask you where you learned about Quadlets. It seems the tutorials are still very sparse.

With the getenfore command from kumi below I get Enforcing so I guess I use SELinux.

I now have two working options. a) Using named volumes (I’m still unsure if this is the way to go or not, generally speaking) and b) using the private label :Z for the bind mount.

Without :Z podman unshare yields root:root for the data directory. After setting the label it is a different user alltogether.

getenforce gives me Enforcing. And I think I have SELinux. I had a look at this tutorial https://www.tutorialworks.com/podman-rootless-volumes/ suggested by another commenter and after running podman unshare ls -al in the folder with the bind mount it returns root root as the owner of the directory. So as far as I understand this means for the podman namespace this folder belongs to root? Like I said in my edit using named volumes solved the issue in on way. I just tried the :Z label too and it seems to work too. So it was probably a SELinux issue?

I was unsure if I installed docker on this machine so I ran docker-compose and the help page showed up (another one than for podman-compose). Then I queried my installed packages and grepped them for docker and nothing shows up. Only podman-compose has docker in the description. So I accidentaly used that compatibility layer already without knowing.

But one reason I consider to switch is because compose files are not really standardized I heard and quadlets are structured like systemd files so I seems more applicable. But that is still a long way.

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.

I tried to use named volumes and now everything works fine, weird.

You could also think about Lunati modding because it uses Lua for this, an easy-to-use programming language. https://docs.luanti.org/for-creators/creating-mods/

+1 for CoMaps

Can you please elaborate on this? I am currently using MicroOS and think about NixOS because of quick setup. But also about Proxmox and NixOS on top. Where would libvirt fit in in this scenario?

This sounds very interesting! I came from DietPi to MicroOS and am now thinking about NixOS, also because of the portability aspect.

I skipped Ansible for now but maybe I have to try that out together with NixOS.

Are you using a VM manager of some sort? I saw libvirtd mentioned in this thread a couple of times.

I tried MicroOS for a while now and I don’t know if it was my fault but I did not work so smoothly all the time. Maybe because the machine was turned off for a few days in a row. But a couple of times I just couldn’t ssh into the machine or it would not start up at all. Luckily ,ou can roll back and I used that to copy my docker volumes and compose files over. I think about trying NixOS next.

I also started with DietPi an every device, works like a charm. But I personally want to try something else to learn a bit more.

Edit:

I think about trying NixOS in the near future.

Can you point me to a tutorial how to setup that up properly for websites? I tried it a while ago and could not get it to work…

I played around with copyparty and I have to say it is just awesome! The config is just fun to mess around with and everything feels snappy.

But I ran into an issue with FTP (probably just something I configured incorrectly) and could not find a discussion for that. I should probably start an issue on Github but as a non-developer I’m not sure how to do that in the correct way.

Edit: I managed to “solve” the problem. Apparently the user uploading to a subfolder over FTP needs the move permission for the folder above said subfolder.

Maybe take a look at this fork: pairdrop

Slowly I am getting confused with all these technologies. What is quadlets if I may ask?

Do you have a recommendation on how to start migrating from docker compose to podman pod or podman kube? And do you know about a web ui for podman (similar to dockge or komodo)?

+1 for dockge. But that’s something for later. Yunohost is a great way to get a feeling for selfhosting.