docker: mapping host uid and gid to user inisde container

Dockerfile

FROM debian:jessie

ENV USER=boatswain USER_ID=1000 USER_GID=1000

# now creating user
RUN groupadd --gid "${USER_GID}" "${USER}" && \
    useradd \
      --uid ${USER_ID} \
      --gid ${USER_GID} \
      --create-home \
      --shell /bin/bash \
      ${USER}

COPY user-mapping.sh /
RUN  chmod u+x user-mapping.sh

ENTRYPOINT ["/user-mapping.sh"]

example use

docker build -t renzok/uid-map . 
docker run --name uid-map --rm -ti -e HOST_USER_ID=22222 -e HOST_USER_GID=22222 renzok/uid-map

or 

docker run --name uid-map --rm -ti -e HOST_USER_ID=$(id -u) -e HOST_USER_GID=$(id -g) -v ${HOME}/devel:/devel renzok/uid-map

user-mapping.sh

#!/bin/bash

if [ -z "${USER}" ]; then
  echo "We need USER to be set!"; exit 100
fi

# if both not set we do not need to do anything
if [ -z "${HOST_USER_ID}" -a -z "${HOST_USER_GID}" ]; then
    echo "Nothing to do here." ; exit 0
fi

# reset user_?id to either new id or if empty old (still one of above
# might not be set)
USER_ID=${HOST_USER_ID:=$USER_ID}
USER_GID=${HOST_USER_GID:=$USER_GID}

LINE=$(grep -F "${USER}" /etc/passwd)
# replace all ':' with a space and create array
array=( ${LINE//:/ } )

# home is 5th element
USER_HOME=${array[4]}

sed -i -e "s/^${USER}:\([^:]*\):[0-9]*:[0-9]*/${USER}:\1:${USER_ID}:${USER_GID}/"  /etc/passwd
sed -i -e "s/^${USER}:\([^:]*\):[0-9]*/${USER}:\1:${USER_GID}/"  /etc/group

chown -R ${USER_ID}:${USER_GID} ${USER_HOME}

exec su - "${USER}"

"RUN chmod u+x user-mapping.sh" should be "RUN chmod u+x /user-mapping.sh" or will get "chmod: cannot access 'user-mapping.sh': No such file or directory"

Thanks so much. It works well.

So good, perfectly solved my problem

Can I pass in a different user in the run command ? I want to use a dummy user in the dockerfile and pass in the actual user .

Thanks!

Is there any difference in directly editing the user file or using the following:

groupmod -g ${USER_GID} ${USER}
usermod -u ${USER_ID} -g ${USER_GID} ${USER}

Awesome solution, thanks @renzok! To make it safe to use/share, do you mind adding a one-liner SPDX license info to these scripts? Just something really simple like this would be helpful:

# SPDX-License-Identifier: AGPL-3.0-or-later

Awesome solution, thanks @renzok! To make it safe to use/share, do you mind adding a one-liner SPDX license info to these scripts? Just something really simple like this would be helpful:

# SPDX-License-Identifier: AGPL-3.0-or-later

Also Many thanks for sharing this, please add a license info.