linuxserver/vscodium-web ¶

Vscodium-web is a community-driven, freely-licensed binary distribution of the remote host web component of Microsoft's editor VS Code.

Supported Architectures¶

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/vscodium-web:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Architecture	Available	Tag
x86-64	✅	amd64-<version tag>
arm64	✅	arm64v8-<version tag>

Application Setup¶

[!NOTE] This image sets up the remote host web component of VSCodium, which is only accessible in a web browser. If you are looking for the full desktop client of VSCodium, served over Selkies, see here: https://github.com/linuxserver/docker-vscodium

If CONNECTION_TOKEN or CONNECTION_TOKEN_FILE env vars are set, you can access the webui at http://<your-ip>:8000/?tkn=supersecrettoken (replace supersecrettoken with the value set). If not, you can access the webui at http://<your-ip>:8000.

For github integration, drop your ssh key in to /config/.ssh. Then open a terminal from the top menu and set your github username and email via the following commands

git config --global user.name "username"
git config --global user.email "email address"

When reverse proxied through SWAG, custom services running on specific ports inside vscodium-web can be accessed at https://PORT.vscodium-web.domain.com very much like how code-server's port proxy function is handled. For that, a wildcard CNAME *.vscodium-web.domain.com needs to be created and the SWAG cert needs to cover those subdomains. Https access to a port can be initiated by adding an s to the end of the PORT in the url (ie. https://PORTs.vscodium-web.domain.com)

Usage¶

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

Info

Unless a parameter is flaged as 'optional', it is mandatory and a value must be provided.

docker-compose (recommended, click here for more info)¶

---
services:
  vscodium-web:
    image: lscr.io/linuxserver/vscodium-web:latest
    container_name: vscodium-web
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - CONNECTION_TOKEN= #optional
      - CONNECTION_TOKEN_FILE= #optional
      - SUDO_PASSWORD=password #optional
      - SUDO_PASSWORD_HASH= #optional
      - CODE_ARGS= #optional
    volumes:
      - /path/to/vscodium-web/config:/config
    ports:
      - 8000:8000
    restart: unless-stopped

docker cli (click here for more info)¶

docker run -d \
  --name=vscodium-web \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e CONNECTION_TOKEN= `#optional` \
  -e CONNECTION_TOKEN_FILE= `#optional` \
  -e SUDO_PASSWORD=password `#optional` \
  -e SUDO_PASSWORD_HASH= `#optional` \
  -e CODE_ARGS= `#optional` \
  -p 8000:8000 \
  -v /path/to/vscodium-web/config:/config \
  --restart unless-stopped \
  lscr.io/linuxserver/vscodium-web:latest

Parameters¶

Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

Ports (`-p`)¶

Parameter	Function
`8000:8000`	Web UI port.

Environment Variables (`-e`)¶

Env	Function
`PUID=1000`	for UserID - see below for explanation
`PGID=1000`	for GroupID - see below for explanation
`TZ=Etc/UTC`	specify a timezone to use, see this list.
`CONNECTION_TOKEN=`	Optional security token for accessing the Web UI (ie. `supersecrettoken`).
`CONNECTION_TOKEN_FILE=`	Optional path to a file inside the container that contains the security token for accessing the Web UI (ie. `/path/to/file`). Overrides `CONNECTION_TOKEN`.
`SUDO_PASSWORD=password`	If this optional variable is set, user will have sudo access in the vscodium-web terminal with the specified password.
`SUDO_PASSWORD_HASH=`	Optionally set sudo password via hash (takes priority over `SUDO_PASSWORD` var). Format is `$type$salt$hashed`.
`CODE_ARGS=`	Optionally add cli parameters to vscodium binary.

Volume Mappings (`-v`)¶

Volume	Function
`/config`	Contains all relevant configuration files.

Miscellaneous Options¶

Parameter	Function

Environment variables from files (Docker secrets)¶

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable

Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.

Umask for running applications¶

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.

User / Group Identifiers¶

When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id your_user as below:

id your_user

Example output:

uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

Docker Mods¶

We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

Support Info¶

Shell access whilst the container is running:
```
docker exec -it vscodium-web /bin/bash
```
To monitor the logs of the container in realtime:
```
docker logs -f vscodium-web
```

Container version number:

docker inspect -f '{{ index .Config.Labels "build_version" }}' vscodium-web

Image version number:

docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/vscodium-web:latest

Updating Info¶

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

Via Docker Compose¶

Update images:

All images:
```
docker-compose pull
```
Single image:
```
docker-compose pull vscodium-web
```

Update containers:

All containers:
```
docker-compose up -d
```
Single container:
```
docker-compose up -d vscodium-web
```

You can also remove the old dangling images:
```
docker image prune
```

Via Docker Run¶

Update the image:

docker pull lscr.io/linuxserver/vscodium-web:latest

Stop the running container:
```
docker stop vscodium-web
```
Delete the container:
```
docker rm vscodium-web
```
Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
You can also remove the old dangling images:
```
docker image prune
```

Image Update Notifications - Diun (Docker Image Update Notifier)¶

Tip

We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

Building locally¶

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-vscodium-web.git
cd docker-vscodium-web
docker build \
  --no-cache \
  --pull \
  -t lscr.io/linuxserver/vscodium-web:latest .

The ARM variants can be built on x86_64 hardware and vice versa using lscr.io/linuxserver/qemu-static

docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

To help with development, we generate this dependency graph.

Init dependency graph

Versions¶

18.12.25: - Initial Release.

linuxserver/vscodium-web¶