Compare commits

...

16 Commits
3.1.9 ... 3.2.3

Author SHA1 Message Date
0fe46e635d Trying to fix issue if data authentication already exist.
Some checks failed
Build and Push Docker Image ARM64 / docker (push) Failing after 1m52s
2025-04-13 04:27:21 +00:00
d84caeb8cf Trying to fix issue when restart. 2025-04-13 03:57:47 +00:00
68e7aa99d8 Trying to fix issue when restart. 2025-04-13 03:30:11 +00:00
8d5deeeef0 Updating version of vscode and adding feature to restart.
Some checks failed
Build and Push Docker Image ARM64 / docker (push) Failing after 1m27s
2025-04-13 00:51:32 +00:00
0c8c0d1068 Updating vscode version.
Some checks failed
Build and Push Docker Image ARM64 / docker (push) Failing after 14m39s
2025-03-07 00:02:34 +00:00
fc0c473ce4 Updating vscode version
Some checks failed
Build and Push Docker Image ARM64 / docker (push) Failing after 2m53s
2025-02-19 20:04:53 +00:00
521c51314a Updating version of vscode. Updating to version 3.1.17 2024-12-17 15:47:33 +00:00
23b4140fc5 Updating version of vscode. 2024-11-19 15:08:35 +00:00
a4e9a02d87 Updating version of vscode. 2024-11-01 10:47:10 -06:00
6fb7085164 Updating version to version 3.1.14 2024-10-03 20:08:51 +00:00
5754ef90a2 Merge branch 'master' of github.com:aleleba/aleleba-vscode-dockerfile-configuration 2024-10-03 20:06:17 +00:00
3b99e2546f Fixing github actions workflow. Updating to version 3.1.13 2024-09-10 14:59:04 -06:00
8ee5f0376f Trying to fix issue, updating to version 3.1.12 2024-09-10 14:46:28 -06:00
b676e5245c Trying to fix build errors. Updating to version 3.1.11 2024-09-10 14:40:24 -06:00
aa71cb3be5 Trying to fix build issues. updating to version 3.1.10 2024-09-10 14:33:03 -06:00
819e72324c Updating to new version of vscode. Updating to version 3.1.3. 2024-06-11 16:21:24 +00:00
4 changed files with 24 additions and 8 deletions

View File

@ -1,8 +1,5 @@
FROM ubuntu:22.04
# Configurar debconf para que use una interfaz no interactiva
ENV DEBIAN_FRONTEND=noninteractive
# Update the package list, install sudo, create a non-root user, and grant password-less sudo permissions
RUN apt update && apt install -y sudo
@ -38,7 +35,7 @@ RUN ARCH="$(dpkg --print-architecture)" \
&& sudo wget -q https://packages.microsoft.com/keys/microsoft.asc -O- | sudo apt-key add - \
&& sudo add-apt-repository "deb [arch=${ARCH}] https://packages.microsoft.com/repos/vscode stable main" \
&& sudo apt-get update \
&& sudo apt-get install -y code
&& sudo DEBIAN_FRONTEND=noninteractive apt-get install -y code
#Making home writable
RUN sudo chmod -R a+rwX /home

View File

@ -157,8 +157,15 @@ else
echo "File extensions.json not found"
fi
if [[ -v VSCODE_TUNNEL_NAME && -n "${VSCODE_TUNNEL_NAME}" ]]; then
sudo su ${HOME_USER} -c "code tunnel --accept-server-license-terms --name ${VSCODE_TUNNEL_NAME}"
# Check if CLI directory exists and has content
if [ -d "/home/${HOME_USER}/.vscode/cli" ] && [ "$(ls -A /home/${HOME_USER}/.vscode/cli 2>/dev/null)" ]; then
# CLI directory exists and has content, use cli data
sudo su ${HOME_USER} -c "code tunnel --cli-data-dir /home/${HOME_USER}/.vscode/cli"
else
sudo su ${HOME_USER} -c "code tunnel --accept-server-license-terms"
# No CLI directory or empty, use normal startup
if [[ -v VSCODE_TUNNEL_NAME && -n "${VSCODE_TUNNEL_NAME}" ]]; then
sudo su ${HOME_USER} -c "code tunnel --accept-server-license-terms --name ${VSCODE_TUNNEL_NAME}"
else
sudo su ${HOME_USER} -c "code tunnel --accept-server-license-terms"
fi
fi

View File

@ -39,6 +39,15 @@ docker run -it -e HOME_USER=custom-home-user -e GLOBAL_ENV_MY_GLOBAL_VARIABLE=my
```
In this example, MY_GLOBAL_VARIABLE will be set to my_global_value in the /etc/environment file.
### Persistent VS Code Tunnel
You can maintain the VS Code tunnel configuration between container restarts by adding a volume mount to `/home/${HOME_USER}/.vscode/cli`. When this volume is mounted and the container restarts, it will use `code tunnel restart` to reconnect using the existing tunnel configuration instead of creating a new one.
Example:
```bash
docker run -it -e HOME_USER=custom-home-user -e VSCODE_TUNNEL_NAME=vscode-ssh-remote-server -v /path/to/vscode-cli:/home/custom-home-user/.vscode/cli -v /path/to/extensions.json:/home/extensions.json aleleba/vscode
```
### 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:
@ -170,6 +179,9 @@ RUN echo 'source ~/.nvm/nvm.sh' >> ~/.bashrc
# Finishing installing node.js and NVM
```
> **Note:** If you are using this image as a base image in a Dockerfile, ensure that the value of `HOME_USER` is the same as the one you will use when creating the container. This is necessary to ensure that all configurations and packages are installed in the correct user directory.
> **Note:** To grant access to the server, please log into https://github.com/login/device and use the code XXXX-XXXX. You can view the container logs to get the code.

View File

@ -1 +1 @@
3.1.9
3.2.3