|
1 | | -[](https://linuxserver.io) |
| 1 | +[linuxserverurl]: https://linuxserver.io |
| 2 | +[forumurl]: https://forum.linuxserver.io |
2 | 3 |
|
3 | | -[](https://blog.linuxserver.io "all the things you can do with our containers including How-To guides, opinions and much more!") |
4 | | -[](https://discord.gg/YWrKVTn "realtime support / chat with the community and the team.") |
5 | | -[](https://discourse.linuxserver.io "post on our community forum.") |
6 | | -[](https://fleet.linuxserver.io "an online web interface which displays all of our maintained images.") |
7 | | -[](https://github.com/linuxserver "view the source for all of our repositories.") |
8 | | -[](https://opencollective.com/linuxserver "please consider helping us by either donating or contributing to our budget") |
| 4 | +[][linuxserverurl] |
9 | 5 |
|
10 | | -The [LinuxServer.io](https://linuxserver.io) team brings you another container release featuring :- |
11 | | - |
12 | | - * regular and timely application updates |
13 | | - * easy user mappings (PGID, PUID) |
14 | | - * custom base image with s6 overlay |
15 | | - * weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth |
16 | | - * regular security updates |
17 | | - |
18 | | -Find us at: |
19 | | -* [Blog](https://blog.linuxserver.io) - all the things you can do with our containers including How-To guides, opinions and much more! |
20 | | -* [Discord](https://discord.gg/YWrKVTn) - realtime support / chat with the community and the team. |
21 | | -* [Discourse](https://discourse.linuxserver.io) - post on our community forum. |
22 | | -* [Fleet](https://fleet.linuxserver.io) - an online web interface which displays all of our maintained images. |
23 | | -* [GitHub](https://github.com/linuxserver) - view the source for all of our repositories. |
24 | | -* [Open Collective](https://opencollective.com/linuxserver) - please consider helping us by either donating or contributing to our budget |
25 | | - |
26 | | -# [linuxserver/code-server](https://github.com/linuxserver/docker-code-server) |
27 | | - |
28 | | -[](https://github.com/linuxserver/docker-code-server) |
29 | | -[](https://github.com/linuxserver/docker-code-server/releases) |
30 | | -[](https://github.com/linuxserver/docker-code-server/packages) |
31 | | -[](https://gitlab.com/Linuxserver.io/docker-code-server/container_registry) |
32 | | -[](https://quay.io/repository/linuxserver.io/code-server) |
33 | | -[](https://microbadger.com/images/linuxserver/code-server "Get your own version badge on microbadger.com") |
34 | | -[](https://hub.docker.com/r/linuxserver/code-server) |
35 | | -[](https://hub.docker.com/r/linuxserver/code-server) |
36 | | -[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-code-server/job/master/) |
37 | | -[](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/code-server/latest/index.html) |
38 | | - |
39 | | -[Code-server](https://coder.com) is VS Code running on a remote server, accessible through the browser. |
40 | | -- Code on your Chromebook, tablet, and laptop with a consistent dev environment. |
41 | | -- If you have a Windows or Mac workstation, more easily develop for Linux. |
42 | | -- Take advantage of large cloud servers to speed up tests, compilations, downloads, and more. |
43 | | -- Preserve battery life when you're on the go. |
44 | | -- All intensive computation runs on your server. |
45 | | -- You're no longer running excess instances of Chrome. |
46 | | - |
47 | | -[](https://coder.com) |
48 | | - |
49 | | -## Supported Architectures |
50 | | - |
51 | | -Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/). |
52 | | - |
53 | | -Simply pulling `linuxserver/code-server` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. |
54 | | - |
55 | | -The architectures supported by this image are: |
56 | | - |
57 | | -| Architecture | Tag | |
58 | | -| :----: | --- | |
59 | | -| x86-64 | amd64-latest | |
60 | | - |
61 | | -## Version Tags |
62 | | - |
63 | | -This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them. |
64 | | - |
65 | | -| Tag | Description | |
66 | | -| :----: | --- | |
67 | | -| latest | Stable releases | |
68 | | -| development | Prereleases from their GitHub | |
69 | | - |
70 | | -## Usage |
71 | | - |
72 | | -Here are some example snippets to help you get started creating a container. |
73 | | - |
74 | | -### docker |
75 | | - |
76 | | -``` |
77 | | -docker create \ |
78 | | - --name=code-server \ |
79 | | - -e PUID=1000 \ |
80 | | - -e PGID=1000 \ |
81 | | - -e TZ=Europe/London \ |
82 | | - -e PASSWORD=password `#optional` \ |
83 | | - -e SUDO_PASSWORD=password `#optional` \ |
84 | | - -p 8443:8443 \ |
85 | | - -v /path/to/appdata/config:/config \ |
86 | | - --restart unless-stopped \ |
87 | | - linuxserver/code-server |
88 | | -``` |
89 | | - |
90 | | - |
91 | | -### docker-compose |
92 | | - |
93 | | -Compatible with docker-compose v2 schemas. |
94 | | - |
95 | | -``` |
96 | | ---- |
97 | | -version: "2" |
98 | | -services: |
99 | | - code-server: |
100 | | - image: linuxserver/code-server |
101 | | - container_name: code-server |
102 | | - environment: |
103 | | - - PUID=1000 |
104 | | - - PGID=1000 |
105 | | - - TZ=Europe/London |
106 | | - - PASSWORD=password #optional |
107 | | - - SUDO_PASSWORD=password #optional |
108 | | - volumes: |
109 | | - - /path/to/appdata/config:/config |
110 | | - ports: |
111 | | - - 8443:8443 |
112 | | - restart: unless-stopped |
113 | | -``` |
114 | | - |
115 | | -## Parameters |
116 | | - |
117 | | -Container images 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. |
118 | | - |
119 | | -| Parameter | Function | |
120 | | -| :----: | --- | |
121 | | -| `-p 8443` | web gui | |
122 | | -| `-e PUID=1000` | for UserID - see below for explanation | |
123 | | -| `-e PGID=1000` | for GroupID - see below for explanation | |
124 | | -| `-e TZ=Europe/London` | Specify a timezone to use EG Europe/London | |
125 | | -| `-e PASSWORD=password` | Optional web gui password, if not provided, there will be no auth. | |
126 | | -| `-e SUDO_PASSWORD=password` | If this optional variable is set, user will have sudo access in the code-server terminal with the specified password. | |
127 | | -| `-v /config` | Contains all relevant configuration files. | |
128 | | - |
129 | | -## Environment variables from files (Docker secrets) |
130 | | - |
131 | | -You can set any environment variable from a file by using a special prepend `FILE__`. |
132 | | - |
133 | | -As an example: |
134 | | - |
135 | | -``` |
136 | | --e FILE__PASSWORD=/run/secrets/mysecretpassword |
137 | | -``` |
138 | | - |
139 | | -Will set the environment variable `PASSWORD` based on the contents of the `/run/secrets/mysecretpassword` file. |
140 | | - |
141 | | -## User / Group Identifiers |
142 | | - |
143 | | -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`. |
144 | | - |
145 | | -Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic. |
146 | | - |
147 | | -In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below: |
148 | | - |
149 | | -``` |
150 | | - $ id username |
151 | | - uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup) |
152 | | -``` |
| 6 | +## Contact information:- |
153 | 7 |
|
| 8 | +| Type | Address/Details | |
| 9 | +| :---: | --- | |
| 10 | +| Discord | [Discord](https://discord.gg/YWrKVTn) | |
| 11 | +| Forum | [Linuserver.io forum][forumurl] | |
154 | 12 |
|
155 | 13 | |
156 | | -## Application Setup |
157 | | - |
158 | | -Access the webui at `http://<your-ip>:8443`. |
159 | | -For github integration, drop your ssh key in to `/config/.ssh`. |
160 | | -Then open a terminal from the top menu and set your github username and email via the following commands |
161 | | -``` |
162 | | -git config --global user.name "username" |
163 | | -git config --global user.email "email address" |
164 | | -``` |
165 | | - |
166 | | - |
167 | | - |
168 | | -## Support Info |
169 | | - |
170 | | -* Shell access whilst the container is running: `docker exec -it code-server /bin/bash` |
171 | | -* To monitor the logs of the container in realtime: `docker logs -f code-server` |
172 | | -* container version number |
173 | | - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' code-server` |
174 | | -* image version number |
175 | | - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/code-server` |
176 | | - |
177 | | -## Updating Info |
178 | | - |
179 | | -Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the [Application Setup](#application-setup) section above to see if it is recommended for the image. |
180 | | - |
181 | | -Below are the instructions for updating containers: |
182 | | - |
183 | | -### Via Docker Run/Create |
184 | | -* Update the image: `docker pull linuxserver/code-server` |
185 | | -* Stop the running container: `docker stop code-server` |
186 | | -* Delete the container: `docker rm code-server` |
187 | | -* Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your `/config` folder and settings will be preserved) |
188 | | -* Start the new container: `docker start code-server` |
189 | | -* You can also remove the old dangling images: `docker image prune` |
190 | | - |
191 | | -### Via Docker Compose |
192 | | -* Update all images: `docker-compose pull` |
193 | | - * or update a single image: `docker-compose pull code-server` |
194 | | -* Let compose update all containers as necessary: `docker-compose up -d` |
195 | | - * or update a single container: `docker-compose up -d code-server` |
196 | | -* You can also remove the old dangling images: `docker image prune` |
197 | | - |
198 | | -### Via Watchtower auto-updater (especially useful if you don't remember the original parameters) |
199 | | -* Pull the latest image at its tag and replace it with the same env variables in one run: |
200 | | - ``` |
201 | | - docker run --rm \ |
202 | | - -v /var/run/docker.sock:/var/run/docker.sock \ |
203 | | - containrrr/watchtower \ |
204 | | - --run-once code-server |
205 | | - ``` |
206 | | - |
207 | | -**Note:** We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose. |
208 | | - |
209 | | -* You can also remove the old dangling images: `docker image prune` |
210 | | - |
211 | | -## Building locally |
212 | | - |
213 | | -If you want to make local modifications to these images for development purposes or just to customize the logic: |
214 | | -``` |
215 | | -git clone https://github.com/linuxserver/docker-code-server.git |
216 | | -cd docker-code-server |
217 | | -docker build \ |
218 | | - --no-cache \ |
219 | | - --pull \ |
220 | | - -t linuxserver/code-server:latest . |
221 | | -``` |
222 | | - |
223 | | -The ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static` |
224 | | -``` |
225 | | -docker run --rm --privileged multiarch/qemu-user-static:register --reset |
226 | | -``` |
| 14 | + |
227 | 15 |
|
228 | | -Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64`. |
| 16 | +The code in this branch is not meant for direct consumption. It is a modification layer to add python2 into `linuxserver/code-server` |
229 | 17 |
|
230 | | -## Versions |
| 18 | +The following line is only in this repo for release messaging: |
231 | 19 |
|
232 | | -* **28.01.20:** - Release python2-mod. |
233 | | -* **17.01.20:** - Fix artifact url retrieval from github. |
234 | | -* **24.10.19:** - Upgrade to v2 builds. |
235 | | -* **28.09.19:** - Update project logo. |
236 | | -* **21.09.19:** - Add development builds/tag. |
237 | | -* **09.07.19:** - Add optional sudo access. |
238 | | -* **01.07.19:** - Add nano. |
239 | | -* **24.06.19:** - Initial Release. |
| 20 | +- { date: "01.01.50:", desc: "I am the release message for this custom branch" } |
0 commit comments