The LinuxServer.io team brings you another container release featuring:
Find us at:
Code-server is VS Code running on a remote server, accessible through the browser.
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/code-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 | ❌ |
Access the webui at http://<your-ip>:8443
.
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"
How to create the hashed password.
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
---
services:
code-server:
image: lscr.io/linuxserver/code-server:latest
container_name: code-server
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- PASSWORD=password #optional
- HASHED_PASSWORD= #optional
- SUDO_PASSWORD=password #optional
- SUDO_PASSWORD_HASH= #optional
- PROXY_DOMAIN=code-server.my.domain #optional
- DEFAULT_WORKSPACE=/config/workspace #optional
volumes:
- /path/to/code-server/config:/config
ports:
- 8443:8443
restart: unless-stopped
docker run -d \
--name=code-server \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Etc/UTC \
-e PASSWORD=password `#optional` \
-e HASHED_PASSWORD= `#optional` \
-e SUDO_PASSWORD=password `#optional` \
-e SUDO_PASSWORD_HASH= `#optional` \
-e PROXY_DOMAIN=code-server.my.domain `#optional` \
-e DEFAULT_WORKSPACE=/config/workspace `#optional` \
-p 8443:8443 \
-v /path/to/code-server/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/code-server:latest
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.
Parameter | Function |
---|---|
-p 8443 |
web gui |
-e PUID=1000 |
for UserID - see below for explanation |
-e PGID=1000 |
for GroupID - see below for explanation |
-e TZ=Etc/UTC |
specify a timezone to use, see this list. |
-e PASSWORD=password |
Optional web gui password, if PASSWORD or HASHED_PASSWORD is not provided, there will be no auth. |
-e HASHED_PASSWORD= |
Optional web gui password, overrides PASSWORD , instructions on how to create it is below. |
-e SUDO_PASSWORD=password |
If this optional variable is set, user will have sudo access in the code-server terminal with the specified password. |
-e SUDO_PASSWORD_HASH= |
Optionally set sudo password via hash (takes priority over SUDO_PASSWORD var). Format is $type$salt$hashed . |
-e PROXY_DOMAIN=code-server.my.domain |
If this optional variable is set, this domain will be proxied for subdomain proxying. See Documentation |
-e DEFAULT_WORKSPACE=/config/workspace |
If this optional variable is set, code-server will open this directory by default |
-v /config |
Contains all relevant configuration files. |
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.
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.
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)
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.
Shell access whilst the container is running:
docker exec -it code-server /bin/bash
To monitor the logs of the container in realtime:
docker logs -f code-server
Container version number:
docker inspect -f '{{ index .Config.Labels "build_version" }}' code-server
Image version number:
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/code-server:latest
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:
Update images:
All images:
docker-compose pull
Single image:
docker-compose pull code-server
Update containers:
All containers:
docker-compose up -d
Single container:
docker-compose up -d code-server
You can also remove the old dangling images:
docker image prune
Update the image:
docker pull lscr.io/linuxserver/code-server:latest
Stop the running container:
docker stop code-server
Delete the container:
docker rm code-server
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
[!TIP] We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
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-code-server.git
cd docker-code-server
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver/code-server: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
.
/config/workspace
contents.install-extension
as a helper for mods to install extensions.DEFAULT_WORKSPACE
env var.chown
on large workspace (contents of workspace folder no longer chowned).HASHED_PASSWORD
.SUDO_PASSWORD_HASH
.