aleleba/aleleba-vscode-dockerfile-configuration
1
0
Fork 0
mirror of https://github.com/aleleba/aleleba-vscode-dockerfile-configuration.git synced 2025-01-09 13:16:48 -06:00
Code Issues Actions Packages Projects Releases Wiki Activity

Cleaning code and fixing vscode user not working. Updating to version. 2.0.34

Browse Source
This commit is contained in:
Alejandro Lembke Barrientos 2024-04-09 21:47:37 +00:00
parent cb4bf58db9
commit 01410a3ccd
Signed by: aleleba
GPG Key ID: F48D7CDEB47942BD
2 changed files with 3 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
entrypoint.sh
View File

@ -1,14 +1,10 @@
#!/bin/bash
set -eu
if [[ -z "${HOME_USER}" ]]; then
if [[ -z "${HOME_USER-}" ]]; then
HOME_USER="vscode"
fi
#addgroup nonroot
#adduser --disabled-password --gecos "" ${HOME_USER}
#echo "${HOME_USER} ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers
# 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)"
@ -43,15 +39,8 @@ if [ "${HOME_USER-}" ]; then
# Changing the HOME_USER in the .bashrc file
sudo su - ${HOME_USER} -c 'sed -i "s|/home/vscode|/home/${HOME_USER}|g" ~/.bashrc'
# Switch to the user specified by $HOME_USER and start an interactive shell session.
sudo -u $HOME_USER -i
# 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 "$HOME_USER" vscode
# sudo groupmod -n "$HOME_USER" vscode
# sudo sed -i "/vscode/d" /etc/sudoers.d/nopasswd
# sudo cd /home/${HOME_USER}
sudo chown -R ${HOME_USER}:${HOME_USER} /home/${HOME_USER}
fi
fi

2
version.txt
View File

@ -1 +1 @@
2.0.32
2.0.34