You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In rootless setups like podman and Docker Rootless, the host's UID is by default mapped to container user root(0). This causes all mounted volumes to be owned by the root user within containers. While it is possible to adjust the default UID mappings, for example, in podman, using --userns to make volumes owned by other users (such as the default user 1000 in the gitea image), this approach requires more configuration and is not user-friendly for deployment.
In my specific use case, I aim to combine Podman Compose with systemd, but I found that modifying the userns settings causes pods created with these adjustments to fail to start. While I acknowledge that this is actually an issue with podman, I would still like to inquire if allowing gitea to run as root could simplify the process.
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Feature Description
In rootless setups like podman and Docker Rootless, the host's UID is by default mapped to container user root(0). This causes all mounted volumes to be owned by the root user within containers. While it is possible to adjust the default UID mappings, for example, in podman, using
--userns
to make volumes owned by other users (such as the default user 1000 in the gitea image), this approach requires more configuration and is not user-friendly for deployment.In my specific use case, I aim to combine Podman Compose with systemd, but I found that modifying the userns settings causes pods created with these adjustments to fail to start. While I acknowledge that this is actually an issue with podman, I would still like to inquire if allowing gitea to run as root could simplify the process.
Screenshots
No response
The text was updated successfully, but these errors were encountered: