It's common for certain images (for example, the LinuxServer group's images to start the container as a user with the same UID to avoid permission issues. However, with the user namespace remap in rootless Docker, this no longer works. For example, if I attempt to start a container as a user with UID 1000, it is remapped to 10099.
Currently, Podman provides a feature which allows a rootless container's user to have the same UID/GID as the user starting the container. Would it be possible to implement this for rootless Docker?
A concrete example: When I map a folder from my host into a Docker container, I have to run as root in the container (which I'm not comfortable with) in order to create any files inside the mapped folder. This feature would solve that issue.
It's common for certain images (for example, the LinuxServer group's images to start the container as a user with the same UID to avoid permission issues. However, with the user namespace remap in rootless Docker, this no longer works. For example, if I attempt to start a container as a user with UID
1000, it is remapped to10099.Currently, Podman provides a feature which allows a rootless container's user to have the same UID/GID as the user starting the container. Would it be possible to implement this for rootless Docker?
A concrete example: When I map a folder from my host into a Docker container, I have to run as root in the container (which I'm not comfortable with) in order to create any files inside the mapped folder. This feature would solve that issue.