Running in Docker creates root-owned files

[MrHedmad]

This is the same issue that always comes up when you use docker. Since the docker daemon runs as root, all the files that it mounts are root-owned. This means that you have to run chown on them all the time.

It would be nice if kerblam could avoid this:

• If we ask every time for your sudo password, we could chown the files ourselves, although it's dangerous if you chown random stuff (security risk)? It would be better to track which files are made and chown those alone, but it's a lot of work.
• If we manage to run the docker container as a user (e.g. see here and here) we could ignore all of this, but it never worked in the past for me.
• We can just ignore this issue but it's a pain in the ass.

[MrHedmad]

This can be avoided by switching to the podman executable instead of docker.
I still have to test out podman, however, but my initial experience is very good.
I'll tag this as RFC.

[MrHedmad]

Just to make the link, the "switch to podman" issue is #37

[MrHedmad]

With #37 being resolved, this is no longer relevant. Making root-owned files is just a side-effect of using docker. With #57 you can swap to Podman and not have this problem anymore.