79443c14ff
If do not update the UID within the passwd database to match whatever uid the container is being ran as, then sudo will not work when renaming the user to match $DOCKER_USER as it will complain about the current user being non-existent.
21 lines
673 B
Bash
Executable File
21 lines
673 B
Bash
Executable File
#!/bin/sh
|
|
set -eu
|
|
|
|
# We do this first to ensure sudo works below when renaming the user.
|
|
# Otherwise the current container UID may not exist in the passwd database.
|
|
eval "$(fixuid -q)"
|
|
|
|
if [ "${DOCKER_USER-}" ]; then
|
|
echo "$DOCKER_USER ALL=(ALL) NOPASSWD:ALL" | sudo tee -a /etc/sudoers.d/nopasswd > /dev/null
|
|
# Unfortunately we cannot change $HOME as we cannot move any bind mounts
|
|
# nor can we bind mount $HOME into a new home as that requires a privileged container.
|
|
sudo usermod --login "$DOCKER_USER" coder
|
|
sudo groupmod -n "$DOCKER_USER" coder
|
|
|
|
USER="$DOCKER_USER"
|
|
|
|
sudo sed -i "/coder/d" /etc/sudoers.d/nopasswd
|
|
fi
|
|
|
|
dumb-init /usr/bin/code-server "$@"
|