mirror of
https://github.com/aleleba/aleleba-vscode-dockerfile-configuration.git
synced 2025-06-19 12:28:15 -06:00
Compare commits
14 Commits
Author | SHA1 | Date | |
---|---|---|---|
0fe46e635d
|
|||
d84caeb8cf
|
|||
68e7aa99d8
|
|||
8d5deeeef0
|
|||
0c8c0d1068
|
|||
fc0c473ce4
|
|||
521c51314a
|
|||
23b4140fc5
|
|||
a4e9a02d87 | |||
6fb7085164
|
|||
5754ef90a2
|
|||
3b99e2546f | |||
8ee5f0376f | |||
819e72324c
|
22
.github/workflows/main-workflow.yml
vendored
22
.github/workflows/main-workflow.yml
vendored
@ -1,4 +1,4 @@
|
||||
name: Build and Push Docker Images
|
||||
name: Build and Push Docker Image ARM64
|
||||
|
||||
on:
|
||||
push:
|
||||
@ -7,26 +7,24 @@ on:
|
||||
jobs:
|
||||
docker:
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
platform: [amd64, arm64]
|
||||
steps:
|
||||
- name: Checkout
|
||||
-
|
||||
name: Checkout
|
||||
uses: actions/checkout@v2
|
||||
|
||||
- name: Set up Docker Buildx
|
||||
-
|
||||
name: Set up Docker Buildx
|
||||
uses: docker/setup-buildx-action@v1
|
||||
|
||||
- name: Login to DockerHub
|
||||
-
|
||||
name: Login to DockerHub
|
||||
uses: docker/login-action@v1
|
||||
with:
|
||||
username: ${{ secrets.DOCKERHUB_USERNAME }}
|
||||
password: ${{ secrets.DOCKERHUB_TOKEN }}
|
||||
|
||||
- name: Build and push
|
||||
-
|
||||
name: Build and push
|
||||
uses: docker/build-push-action@v2
|
||||
with:
|
||||
context: .
|
||||
push: true
|
||||
tags: aleleba/vscode:latest
|
||||
platforms: linux/${{ matrix.platform }}
|
||||
platforms: linux/amd64,linux/arm64
|
@ -1,9 +1,5 @@
|
||||
FROM ubuntu:22.04
|
||||
|
||||
# Configurar debconf para que use una interfaz no interactiva
|
||||
ENV DEBIAN_FRONTEND=noninteractive
|
||||
ENV DEBCONF_NONINTERACTIVE_SEEN=true
|
||||
|
||||
# Update the package list, install sudo, create a non-root user, and grant password-less sudo permissions
|
||||
RUN apt update && apt install -y sudo
|
||||
|
||||
@ -39,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
|
||||
|
@ -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
|
||||
|
12
readme.md
12
readme.md
@ -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.
|
||||
|
@ -1 +1 @@
|
||||
3.1.11
|
||||
3.2.3
|
||||
|
Reference in New Issue
Block a user