Compare commits

...

6 Commits
3.2.1 ... 3.2.7

Author SHA1 Message Date
f3797b5660 Removing feature to persist session since is not possible because OAuth process of github.
Some checks failed
Build and Push Docker Image ARM64 / docker (push) Failing after 3m19s
2025-04-14 16:46:35 +00:00
a1e53a6624 Trying to fix issue of recreate the tunnel.
Some checks failed
Build and Push Docker Image ARM64 / docker (push) Failing after 3m14s
2025-04-14 01:13:35 +00:00
3da90aa1a4 Fixing typo. 2025-04-14 00:06:02 +00:00
aa9afba282 Trying to fix existing tunnel. 2025-04-13 23:44:58 +00:00
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
3 changed files with 4 additions and 35 deletions

View File

@ -157,30 +157,8 @@ else
echo "File extensions.json not found" echo "File extensions.json not found"
fi fi
# Check if CLI directory exists and has content if [[ -v VSCODE_TUNNEL_NAME && -n "${VSCODE_TUNNEL_NAME}" ]]; then
if [ -d "/home/${HOME_USER}/.vscode/cli" ] && [ "$(ls -A /home/${HOME_USER}/.vscode/cli 2>/dev/null)" ]; then
# CLI directory exists and has content, ensure proper permissions first
sudo chmod -R a+rwX /home/${HOME_USER}/.vscode/cli
# Wait briefly to ensure services are up
sleep 2
echo "Restarting VS Code tunnel..."
# Try to restart, but fall back to normal startup if it fails
if ! sudo su ${HOME_USER} -c "code tunnel restart"; then
echo "Tunnel restart failed, trying 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}" 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
else else
# No CLI directory or empty, use normal startup
echo "Starting new VS Code tunnel session..."
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" sudo su ${HOME_USER} -c "code tunnel --accept-server-license-terms"
fi
fi fi

View File

@ -39,15 +39,6 @@ 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. 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 ### 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: 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:

View File

@ -1 +1 @@
3.2.1 3.2.7