linuxserver/openvscode-server¶
Openvscode-server provides a version of VS Code that runs a server on a remote machine and allows access through a modern web browser.
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/openvscode-server: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> |
armhf | ❌ |
Version Tags¶
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
Tag | Available | Description |
---|---|---|
latest | ✅ | Stable releases |
insiders | ✅ | Insiders releases |
Application Setup¶
If CONNECTION_TOKEN
or CONNECTION_SECRET
env vars are set, you can access the webui at http://<your-ip>:3000/?tkn=supersecrettoken
(replace supersecrettoken
with the value set). If not, you can access the webui at http://<your-ip>:3000
.
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
When reverse proxied through SWAG, custom services running on specific ports inside openvscode-server can be accessed at https://PORT.openvscode-server.domain.com
very much like how code-server's port proxy function is handled. For that, a wildcard CNAME *.openvscode-server.domain.com
needs to be created and the SWAG cert needs to cover those subdomains.
Usage¶
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
docker-compose (recommended, click here for more info)¶
---
services:
openvscode-server:
image: lscr.io/linuxserver/openvscode-server:latest
container_name: openvscode-server
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- CONNECTION_TOKEN= #optional
- CONNECTION_SECRET= #optional
- SUDO_PASSWORD=password #optional
- SUDO_PASSWORD_HASH= #optional
volumes:
- /path/to/appdata/config:/config
ports:
- 3000:3000
restart: unless-stopped
docker cli (click here for more info)¶
docker run -d \
--name=openvscode-server \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Etc/UTC \
-e CONNECTION_TOKEN= `#optional` \
-e CONNECTION_SECRET= `#optional` \
-e SUDO_PASSWORD=password `#optional` \
-e SUDO_PASSWORD_HASH= `#optional` \
-p 3000:3000 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/openvscode-server: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 |
---|---|
3000 | 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_SECRET= | 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 openvscode-server 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 . |
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:
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:
Example output:
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:
-
To monitor the logs of the container in realtime:
-
Container version number:
-
Image version number:
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:
-
Single image:
-
-
Update containers:
-
All containers:
-
Single container:
-
-
You can also remove the old dangling images:
Via Docker Run¶
-
Update the image:
-
Stop the running container:
-
Delete the container:
-
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:
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-openvscode-server.git
cd docker-openvscode-server
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver/openvscode-server:latest .
The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64
.
Versions¶
- 01.07.23: - Deprecate armhf. As announced here
- 29.09.22: - Rebase to jammy, switch to s6v3. Fix chown logic to skip
/config/workspace
contents. - 12.02.22: - Update
install-extension
helper to compensate for upstream changes. - 04.02.22: - Update binary for 1.64.0+. Allow for no token set when both toekn env vars are unset. Add libsecret for keytar.
- 29.12.21: - Add
install-extension
as a helper for mods to install extensions. - 10.12.21: - Update deprecated connectionToken arg.
- 30.11.21: - Fix app folder permissions, add the optional sudo password vars.
- 29.11.21: - Create
.profile
and.bashrc
for the user. - 29.11.21: - Release
insiders
tag. - 28.11.21: - Initial Release.