Compare commits

..

40 Commits

Author SHA1 Message Date
52b9e7a411 Trying to fix users issue. Updating to version 2.0.18 2024-04-05 21:03:19 +00:00
04e26f2afc Trying to fix issue. Updating to version 2.0.17 2024-03-30 04:56:24 +00:00
dddaf129f4 Trying to fix. Updating to version 2.0.16 2024-03-30 03:15:32 +00:00
6525dc4c7e Trying to fix issue. updating to version 2.0.15 2024-03-30 01:28:33 +00:00
b3609b3d0b Trying to fix adding environment variables to app. 2024-03-29 22:35:02 +00:00
dd283a2c5f Adding the environment variables of vscode to home user. Updating to version 2.0.13 2024-03-19 19:50:04 +00:00
18fe10675c Updating version to version 2.0.12 and trying to fix isuue. 2024-03-05 22:23:30 +00:00
aabc21eac2 Trying to fix the issue. Updating to version 2.0.11 2024-03-05 20:47:59 +00:00
50708112ac Trying to fix again the issue. Updating to version 2.0.10 2024-03-05 20:02:48 +00:00
f29f99181e Trying to fix. Updatin to version 2.0.9 2024-02-15 23:27:33 +00:00
8e9ef7bfa9 Trying to fix issue. updating to version 2.0.8 2024-02-15 20:18:50 +00:00
762ff44dc8 Fixing sudo issue. 2024-02-15 18:56:28 +00:00
ac7a82f0ca Trying to fix issue. Updating to version 2.0.6 2024-02-15 18:41:29 +00:00
9bac2433a6 Trying to fix. Updating to version 2.0.5 2024-02-15 06:23:40 +00:00
d8a291c82d Trying to fix. Version 2.0.4 2024-02-15 04:07:06 +00:00
3cee54d519 Trying to fix it. 2.0.3 2024-02-15 03:50:50 +00:00
f68ef82de3 Trying to make fix, updating to version 2.0.2 2024-02-15 03:21:00 +00:00
47d6a61a28 Trying to fix user error. Updating to version 2.0.1 2024-02-15 01:44:59 +00:00
b5cbdca7ef Trying to fix user configuration. Updating to version 2.0.0 2024-02-15 01:05:41 +00:00
68bdbd4c61 Trying to fix issue. Updating to version 1.1.6 2024-02-14 21:32:17 +00:00
a164ccadff trying to make user dynamic. 2024-02-14 21:15:23 +00:00
d755728ed8 Returning to the working configuration. Updating to version 1.1.4 2024-02-14 18:48:08 +00:00
c17566fd5f Trying to fix the creation of the user, updating to version 1.1.3 2024-02-14 17:51:26 +00:00
f9351861bd Updating entrypoint.sh updating to version 1.1.2 2024-02-14 16:55:47 +00:00
1634a2a507 Fixing typo. Updating to version 1.1.1 2023-09-01 18:11:04 +00:00
8bda7b330b Changing the extensions.json structure to have more order. Updating to version 1.1.0 2023-09-01 17:07:46 +00:00
e1245da9de Adding Readme file. Updating to version 1.0.25. 2023-08-30 19:56:08 +00:00
8d86fd2f5d Fixing typo. Updating to version 1.0.24 2023-08-30 03:55:28 +00:00
f5a6331fd3 Trying to fix the instalation of extensions. Updating to version 1.0.22 2023-08-29 19:39:54 +00:00
8676e1bcb3 Trying to fix the instalation of extensions. Updating to version 1.0.22 2023-08-29 18:31:12 +00:00
52d6bc12f4 Trying to fix the instalation of extensions. Updating to version 1.0.21 2023-08-29 17:15:51 +00:00
fdcea0d423 Fixing typo. updating to version 1.0.20 2023-08-29 16:17:01 +00:00
1a8869bb11 Trying to fix the instalation of extensions. Updating to version 1.0.19 2023-08-29 16:11:28 +00:00
53afd74739 Trying to install extensions. Update to version 1.0.18. 2023-08-29 15:15:48 +00:00
00defc98eb Fixing adding the missing dependency of jq. 2023-08-29 14:19:33 +00:00
127a78f58d Copying files of extensions to vscode-server and to vscode-server-insiders. Updating to version 1.0.16 2023-08-29 13:39:05 +00:00
d5e345fb48 Adding to bash the functionality to install extensions from array. Updating to version 1.0.15 2023-08-29 12:56:31 +00:00
e0bb4bfa2f Trying to fix entrypont.sh Updating to version 1.0.14 2023-08-27 04:53:21 +00:00
c90139bbcc Trying to fix entrypoint.sh Updating to version 1.0.13. 2023-08-27 03:50:03 +00:00
3dc1c03a0f Trying to fix entrypoint.sh Updating to version 1.0.12 2023-08-27 00:29:06 +00:00
4 changed files with 220 additions and 7 deletions

View File

@ -9,6 +9,21 @@ RUN sudo apt-get update
RUN sudo apt-get install -y curl
#Instalando wget
RUN sudo apt-get install -y wget
#Instalando jq
RUN sudo apt-get install -y jq
RUN sudo apt-get update
RUN sudo apt-get install dumb-init
RUN adduser --gecos '' --disabled-password vscode \
&& echo "vscode ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers.d/nopasswd
RUN ARCH="$(dpkg --print-architecture)" \
&& curl -fsSL "https://github.com/boxboat/fixuid/releases/download/v0.6.0/fixuid-0.6.0-linux-$ARCH.tar.gz" | tar -C /usr/local/bin -xzf - \
&& chown root:root /usr/local/bin/fixuid \
&& chmod 4755 /usr/local/bin/fixuid \
&& mkdir -p /etc/fixuid \
&& printf "user: vscode\ngroup: vscode\n" > /etc/fixuid/config.yml
#Instalando devtunnel
#Comandos que no se deben olvidar correr al crear el devtunnel
@ -32,4 +47,8 @@ RUN sudo sysctl -w fs.inotify.max_user_watches=524288
ADD ./entrypoint.sh /usr/bin/entrypoint.sh
RUN sudo chmod +x /usr/bin/entrypoint.sh
USER 1000
ENV USER=vscode
WORKDIR /home/vscode
ENTRYPOINT ["/usr/bin/entrypoint.sh"]

96
entrypoint.sh Normal file → Executable file
View File

@ -1,16 +1,100 @@
#!/bin/bash
set -eu
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
#addgroup nonroot
#adduser --disabled-password --gecos "" ${HOME_USER}
#echo "${HOME_USER} ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers
su - ${HOME_USER}
# 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 [ "${HOME_USER-}" ]; then
USER="$HOME_USER"
if [ "$HOME_USER" != "$(whoami)" ]; then
if ! id -u $HOME_USER > /dev/null 2>&1; then
# Create a user with the same UID as the host user.
# sudo adduser --disabled-password --gecos "" ${HOME_USER}
# sudo echo "$HOME_USER ALL=(ALL) NOPASSWD:ALL" | sudo tee -a /etc/sudoers.d/nopasswd > /dev/null
# Set the default shell to bash for VS Code Remote - Containers
sudo usermod --login "$HOME_USER" vscode
sudo groupmod -n "$HOME_USER" vscode
sudo sed -i "/vscode/d" /etc/sudoers.d/nopasswd
# Crear el nuevo directorio home si no existe
# if [ -d "/home/${HOME_USER}" ]; then
# Si existe, hacer una copia de seguridad de los archivos existentes
# sudo mv /home/${HOME_USER} /home/${HOME_USER}_backup
# fi
# Cambiar el directorio home del usuario vscode a /home/${HOME_USER}
sudo usermod -d /home/${HOME_USER} -m vscode
su - ${HOME_USER}
fi
# Copy environment variables from vscode user to HOME_USER
#env | grep -v 'HOME_USER' | while read -r line; do
#sudo su - ${HOME_USER} -c "echo 'export $line' >> ~/.bashrc"
#done
#sudo -u $HOME_USER -i
# sudo cd /home/${HOME_USER}
sudo chown -R ${HOME_USER}:${HOME_USER} /home/${HOME_USER}
fi
fi
#Creating extensions folder
if [ ! -d "/home/${HOME_USER}/.config/Code" ]; then
sudo mkdir -p /home/${HOME_USER}/.config/Code
fi
sudo chmod -R a+rwX /home/${HOME_USER}/.config/Code
if [ ! -d "/home/${HOME_USER}/.vscode-server" ]; then
sudo mkdir -p /home/${HOME_USER}/.vscode-server
fi
sudo chmod -R a+rwX /home/${HOME_USER}/.vscode-server
if [ ! -d "/home/${HOME_USER}/.vscode-server-insiders" ]; then
sudo mkdir -p /home/${HOME_USER}/.vscode-server-insiders
fi
sudo chmod -R a+rwX /home/${HOME_USER}/.vscode-server-insiders
# Check if the data.json file exists
if [ -f "/home/extensions.json" ]; then
# Read the JSON file into a variable
jsonExtensions=$(cat /home/extensions.json)
# Use jq to extract the extension parameter from the JSON array
extensions=$(echo $jsonExtensions | jq -r '.[].extensionsGroup.extensions[].uniqueIdentifier')
# Loop through the extensions and process each element
for extension in $extensions; do
echo "Installing extension: $extension"
sudo su - ${HOME_USER} -c "code --install-extension $extension"
done
sudo cp -R /home/${HOME_USER}/.vscode/* /home/${HOME_USER}/.vscode-server
sudo cp -R /home/${HOME_USER}/.vscode/* /home/${HOME_USER}/.vscode-server-insiders
sudo chmod -R a+rwX /home/${HOME_USER}/.vscode
sudo chmod -R a+rwX /home/${HOME_USER}/.vscode-server
sudo chmod -R a+rwX /home/${HOME_USER}/.vscode-server-insiders
else
echo "File extensions.json not found"
fi
# Allow users to have scripts run on container startup to prepare workspace.
# https://github.com/coder/code-server/issues/5177
#if [ -d "${ENTRYPOINTD}" ]; then
#find "${ENTRYPOINTD}" -type f -executable -print -exec {} \;
#fi
if [[ -z "${VSCODE_TUNNEL_NAME}" ]]; then
code tunnel --accept-server-license-terms
exec dumb-init sudo su - ${HOME_USER} -c "code tunnel --accept-server-license-terms $@"
else
code tunnel --accept-server-license-terms --name ${VSCODE_TUNNEL_NAME}
exec dumb-init sudo su - ${HOME_USER} -c "code tunnel --accept-server-license-terms --name ${VSCODE_TUNNEL_NAME} $@"
fi

110
readme.md Normal file
View File

@ -0,0 +1,110 @@
# Aleleba VSCode Dockerfile Configuration
This repository contains a Dockerfile configuration for use with Visual Studio Code with dev tunnel.
## Getting Started
To run the Docker container, follow these steps:
1. Clone this repository to your local machine.
2. Open the integrated terminal in Visual Studio Code.
3. Run the Docker container by running the following command: `docker run -it -e HOME_USER=custom-home-user -e VSCODE_TUNNEL_NAME=vscode-ssh-remote-server -v /path/to/extensions.json:/home/extensions.json aleleba/vscode`
### Environment Variables
The following environment variables can be set when running the Docker container:
- `HOME_USER`: The username of the user running the container. This is used to set the correct permissions on files created in the container.
- `VSCODE_TUNNEL_NAME`: The name of the SSH tunnel used by Visual Studio Code to connect to the container.
### Adding VSCode Extensions
To add VSCode extensions to the container, create a JSON file with an array of objects containing the extension details you want to install, the only Mandatory field is uniqueIdentifier and follow this structure. For example:
```
[
{
"extensionsGroup": {
"description": "Extensions of Spanish Language Pack",
"extensions": [
{
"name": "Spanish Language Pack for Visual Studio Code",
"notes": "Extension of Spanish Language Pack for Visual Studio Code",
"uniqueIdentifier": "ms-ceintl.vscode-language-pack-es"
}
]
}
},
{
"extensionsGroup": {
"description": "Extensions of Github Copilot",
"extensions": [
{
"name": "GitHub Copilot",
"notes": "Extension of GitHub Copilot",
"uniqueIdentifier": "github.copilot"
},
{
"name": "GitHub Copilot Chat",
"notes": "Extension of GitHub Copilot Chat",
"uniqueIdentifier": "github.copilot-chat"
}
]
}
}
]
```
Save this file as `extensions.json` and add it as a volume when running the Docker container on /home/extensions.json. For example:
`docker run -it -e HOME_USER=custom-home-user -e VSCODE_TUNNEL_NAME=vscode-ssh-remote-server -v /path/to/extensions.json:/home/extensions.json aleleba/vscode`
The extensions will be installed automatically after the container is created.
### Using Docker Compose
Alternatively, you can use Docker Compose to run the container with the `aleleba/vscode` image and the `HOME_USER` and `VSCODE_TUNNEL_NAME` environment variables set. Here's an example `docker-compose.yml` file:
```
version: '3'
services:
vscode:
image: aleleba/vscode
environment:
HOME_USER: custom-home-user
VSCODE_TUNNEL_NAME: vscode-ssh-remote-server
volumes:
- /path/to/extensions.json:/home/extensions.json
```
You can run this `docker-compose.yml` file by navigating to the directory where it is saved and running the following command: `docker-compose up -d`
This will start the container in the background and output the container ID. You can then use the `docker ps` command to view the running container.
## Using this image as a base image in a Dockerfile
To use this image as a base image in a Dockerfile, you can add the following line to the top of your Dockerfile and you can install any additional packages you need, here an example installing nvm and nodejs in a `Dockerfile`:
```
FROM aleleba/vscode:latest
# Installing node.js and NVM
SHELL ["/bin/bash", "--login", "-i", "-c"]
RUN curl https://raw.githubusercontent.com/creationix/nvm/master/install.sh | bash
RUN nvm install --lts
RUN nvm alias default lts/*
SHELL ["/bin/sh", "-c"]
RUN echo 'source ~/.nvm/nvm.sh' >> ~/.bashrc
# Finishing installing node.js and NVM
```
## Contributing
If you'd like to contribute to this project, please fork the repository and create a pull request.
## License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
I hope this helps! Let me know if you have any further questions.

View File

@ -1 +1 @@
1.0.11
2.0.18