Compare commits

...

5 Commits

3 changed files with 154 additions and 8 deletions

View File

@ -1,11 +1,47 @@
#!/bin/bash #!/bin/bash
if [[ -z "${HOME_USER}" ]]; then #if [[ -z "${HOME_USER}" ]]; then
HOME_USER="vscode" #HOME_USER="vscode"
#fi
set -e
# use specified user name or use `vscode` if not specified
HOME_USER="${HOME_USER:-vscode}"
# use specified group name or use the same user name also as the group name
MY_GROUP="${MY_GROUP:-${HOME_USER}}"
# use the specified UID for the user
MY_UID="${MY_UID:-1000}"
# use the specified GID for the user
MY_GID="${MY_GID:-${MY_UID}}"
# check to see if group exists; if not, create it
if grep -q -E "^${MY_GROUP}:" /etc/group > /dev/null 2>&1
then
echo "INFO: Group exists; skipping creation"
else
echo "INFO: Group doesn't exist; creating..."
# create the group
sudo addgroup -g "${MY_GID}" "${MY_GROUP}" || (echo "INFO: Group exists but with a different name; renaming..."; sudo groupmod -g "${MY_GID}" -n "${MY_GROUP}" "$(awk -F ':' '{print $1":"$3}' < /etc/group | grep ":${MY_GID}$" | awk -F ":" '{print $1}')")
fi fi
addgroup nonroot
adduser --disabled-password --gecos "" ${HOME_USER} # check to see if user exists; if not, create it
echo "${HOME_USER} ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers if id -u "${HOME_USER}" > /dev/null 2>&1
then
echo "INFO: User exists; skipping creation"
else
echo "INFO: User doesn't exist; creating..."
# create the user
sudo adduser -u "${MY_UID}" -G "${MY_GROUP}" -h "/home/${HOME_USER}" -s /bin/sh -D "${HOME_USER}"
fi
# addgroup nonroot
#adduser --disabled-password --gecos "" ${HOME_USER}
# echo "${HOME_USER} ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers
#Creating extensions folder #Creating extensions folder
sudo mkdir /home/${HOME_USER}/.config/Code sudo mkdir /home/${HOME_USER}/.config/Code
@ -20,8 +56,8 @@ if [ -f "/home/extensions.json" ]; then
# Read the JSON file into a variable # Read the JSON file into a variable
jsonExtensions=$(cat /home/extensions.json) jsonExtensions=$(cat /home/extensions.json)
# Use jq to extract the array elements # Use jq to extract the extension parameter from the JSON array
extensions=$(echo $jsonExtensions | jq -r '.[]') extensions=$(echo $jsonExtensions | jq -r '.[].extensionsGroup.extensions[].uniqueIdentifier')
# Loop through the extensions and process each element # Loop through the extensions and process each element
for extension in $extensions; do for extension in $extensions; do

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.24 1.1.3