Skip to content

Commit 4472027

Browse files
committed
testing port and readme updates
1 parent 91f964c commit 4472027

4 files changed

Lines changed: 54 additions & 170 deletions

File tree

Jenkinsfile

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,8 @@ pipeline {
3030
MULTIARCH='true'
3131
CI='true'
3232
CI_WEB='true'
33-
CI_PORT='3000'
34-
CI_SSL='false'
33+
CI_PORT='3001'
34+
CI_SSL='true'
3535
CI_DELAY='120'
3636
CI_SBOM_TIMEOUT='1800'
3737
CI_DOCKERENV='TZ=US/Pacific'

README.md

Lines changed: 7 additions & 91 deletions
Original file line numberDiff line numberDiff line change
@@ -59,12 +59,10 @@ The architectures supported by this image are:
5959

6060
## Application Setup
6161

62-
The Kali Linux image can be accessed at:
62+
The application can be accessed at:
6363

64-
* http://yourhost:3000/
6564
* https://yourhost:3001/
6665

67-
**Modern GUI desktop apps have issues with the latest Docker and syscall compatibility, you can use Docker with the `--security-opt seccomp=unconfined` setting to allow these syscalls on hosts with older Kernels or libseccomp**
6866

6967
### Security
7068

@@ -73,68 +71,7 @@ The Kali Linux image can be accessed at:
7371
7472
By default this container has no authentication and the optional environment variables `CUSTOM_USER` and `PASSWORD` to enable basic http auth via the embedded NGINX server should only be used to locally secure the container from unwanted access on a local network. If exposing this to the Internet we recommend putting it behind a reverse proxy, such as [SWAG](https://github.com/linuxserver/docker-swag), and ensuring a secure authentication solution is in place. From the web interface a terminal can be launched and it is configured for passwordless sudo, so anyone with access to it can install and run whatever they want along with probing your local network.
7573

76-
### Options in all KasmVNC based GUI containers
77-
78-
This container is based on [Docker Baseimage KasmVNC](https://github.com/linuxserver/docker-baseimage-kasmvnc) which means there are additional environment variables and run configurations to enable or disable specific functionality.
79-
80-
#### Optional environment variables
81-
82-
| Variable | Description |
83-
| :----: | --- |
84-
| CUSTOM_PORT | Internal port the container listens on for http if it needs to be swapped from the default 3000. |
85-
| CUSTOM_HTTPS_PORT | Internal port the container listens on for https if it needs to be swapped from the default 3001. |
86-
| CUSTOM_USER | HTTP Basic auth username, abc is default. |
87-
| PASSWORD | HTTP Basic auth password, abc is default. If unset there will be no auth |
88-
| SUBFOLDER | Subfolder for the application if running a subfolder reverse proxy, need both slashes IE `/subfolder/` |
89-
| TITLE | The page title displayed on the web browser, default "KasmVNC Client". |
90-
| FM_HOME | This is the home directory (landing) for the file manager, default "/config". |
91-
| START_DOCKER | If set to false a container with privilege will not automatically start the DinD Docker setup. |
92-
| DRINODE | If mounting in /dev/dri for [DRI3 GPU Acceleration](https://www.kasmweb.com/kasmvnc/docs/master/gpu_acceleration.html) allows you to specify the device to use IE `/dev/dri/renderD128` |
93-
| DISABLE_IPV6 | If set to true or any value this will disable IPv6 |
94-
| LC_ALL | Set the Language for the container to run as IE `fr_FR.UTF-8` `ar_AE.UTF-8` |
95-
| NO_DECOR | If set the application will run without window borders in openbox for use as a PWA. |
96-
| NO_FULL | Do not autmatically fullscreen applications when using openbox. |
97-
98-
#### Optional run configurations
99-
100-
| Variable | Description |
101-
| :----: | --- |
102-
| `--privileged` | Will start a Docker in Docker (DinD) setup inside the container to use docker in an isolated environment. For increased performance mount the Docker directory inside the container to the host IE `-v /home/user/docker-data:/var/lib/docker`. |
103-
| `-v /var/run/docker.sock:/var/run/docker.sock` | Mount in the host level Docker socket to either interact with it via CLI or use Docker enabled applications. |
104-
| `--device /dev/dri:/dev/dri` | Mount a GPU into the container, this can be used in conjunction with the `DRINODE` environment variable to leverage a host video card for GPU accelerated applications. Only **Open Source** drivers are supported IE (Intel,AMDGPU,Radeon,ATI,Nouveau) |
105-
106-
### Language Support - Internationalization
107-
108-
The environment variable `LC_ALL` can be used to start this container in a different language than English simply pass for example to launch the Desktop session in French `LC_ALL=fr_FR.UTF-8`. Some languages like Chinese, Japanese, or Korean will be missing fonts needed to render properly known as cjk fonts, but others may exist and not be installed inside the container depending on what underlying distribution you are running. We only ensure fonts for Latin characters are present. Fonts can be installed with a mod on startup.
109-
110-
To install cjk fonts on startup as an example pass the environment variables (Alpine base):
111-
112-
```
113-
-e DOCKER_MODS=linuxserver/mods:universal-package-install
114-
-e INSTALL_PACKAGES=fonts-noto-cjk
115-
-e LC_ALL=zh_CN.UTF-8
116-
```
117-
118-
The web interface has the option for "IME Input Mode" in Settings which will allow non english characters to be used from a non en_US keyboard on the client. Once enabled it will perform the same as a local Linux installation set to your locale.
119-
120-
### DRI3 GPU Acceleration (KasmVNC interface)
121-
122-
For accelerated apps or games, render devices can be mounted into the container and leveraged by applications using:
123-
124-
`--device /dev/dri:/dev/dri`
125-
126-
This feature only supports **Open Source** GPU drivers:
127-
128-
| Driver | Description |
129-
| :----: | --- |
130-
| Intel | i965 and i915 drivers for Intel iGPU chipsets |
131-
| AMD | AMDGPU, Radeon, and ATI drivers for AMD dedicated or APU chipsets |
132-
| NVIDIA | nouveau2 drivers only, closed source NVIDIA drivers lack DRI3 support |
133-
134-
The `DRINODE` environment variable can be used to point to a specific GPU.
135-
Up to date information can be found [here](https://www.kasmweb.com/kasmvnc/docs/master/gpu_acceleration.html)
136-
137-
### Nvidia GPU Support (KasmVNC interface)
74+
### Nvidia GPU Support
13875

13976
**Nvidia support is not compatible with Alpine based images as Alpine lacks Nvidia drivers**
14077

@@ -156,8 +93,8 @@ And to assign the GPU in compose:
15693

15794
```
15895
services:
159-
kali-linux:
160-
image: lscr.io/linuxserver/kali-linux:latest
96+
webtop:
97+
image: lscr.io/linuxserver/suyu:latest
16198
deploy:
16299
resources:
163100
reservations:
@@ -167,27 +104,10 @@ services:
167104
capabilities: [compute,video,graphics,utility]
168105
```
169106

170-
### Application management
171-
172-
#### PRoot Apps
173-
174-
If you run system native installations of software IE `sudo apt-get install filezilla` and then upgrade or destroy/re-create the container that software will be removed and the container will be at a clean state. For some users that will be acceptable and they can update their system packages as well using system native commands like `apt-get upgrade`. If you want Docker to handle upgrading the container and retain your applications and settings we have created [proot-apps](https://github.com/linuxserver/proot-apps) which allow portable applications to be installed to persistent storage in the user's `$HOME` directory and they will work in a confined Docker environment out of the box. These applications and their settings will persist upgrades of the base container and can be mounted into different flavors of KasmVNC based containers on the fly. This can be achieved from the command line with:
107+
### Strict reverse proxies
175108

176-
```
177-
proot-apps install filezilla
178-
```
179-
180-
PRoot Apps is included in all KasmVNC based containers, a list of linuxserver.io supported applications is located [HERE](https://github.com/linuxserver/proot-apps?tab=readme-ov-file#supported-apps).
181-
182-
#### Native Apps
183-
184-
It is possible to install extra packages during container start using [universal-package-install](https://github.com/linuxserver/docker-mods/tree/universal-package-install). It might increase starting time significantly. PRoot is preferred.
185-
186-
```yaml
187-
environment:
188-
- DOCKER_MODS=linuxserver/mods:universal-package-install
189-
- INSTALL_PACKAGES=libfuse2|git|gdb
190-
```
109+
This image uses a self-signed certificate by default. This naturally means the scheme is `https`.
110+
If you are using a reverse proxy which validates certificates, you need to [disable this check for the container](https://docs.linuxserver.io/faq#strict-proxy).
191111

192112
## Usage
193113

@@ -218,8 +138,6 @@ services:
218138
ports:
219139
- 3000:3000
220140
- 3001:3001
221-
devices:
222-
- /dev/dri:/dev/dri #optional
223141
shm_size: "1gb" #optional
224142
restart: unless-stopped
225143
```
@@ -239,7 +157,6 @@ docker run -d \
239157
-p 3001:3001 \
240158
-v /path/to/data:/config \
241159
-v /var/run/docker.sock:/var/run/docker.sock `#optional` \
242-
--device /dev/dri:/dev/dri `#optional` \
243160
--shm-size="1gb" `#optional` \
244161
--restart unless-stopped \
245162
lscr.io/linuxserver/kali-linux:latest
@@ -260,7 +177,6 @@ Containers are configured using parameters passed at runtime (such as those abov
260177
| `-e TITLE=Kali Linux` | String which will be used as page/tab title in the web browser. |
261178
| `-v /config` | abc users home directory |
262179
| `-v /var/run/docker.sock` | Docker Socket on the system, if you want to use Docker in the container |
263-
| `--device /dev/dri` | Add this for GL support (Linux hosts only) |
264180
| `--shm-size=` | We set this to 1 gig to prevent modern web browsers from crashing |
265181
| `--security-opt seccomp=unconfined` | For Docker Engine only, many modern gui apps need this to function on older hosts as syscalls are unknown to Docker. |
266182

jenkins-vars.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,8 @@ repo_vars:
1919
- MULTIARCH='true'
2020
- CI='true'
2121
- CI_WEB='true'
22-
- CI_PORT='3000'
23-
- CI_SSL='false'
22+
- CI_PORT='3001'
23+
- CI_SSL='true'
2424
- CI_DELAY='120'
2525
- CI_SBOM_TIMEOUT='1800'
2626
- CI_DOCKERENV='TZ=US/Pacific'

readme-vars.yml

Lines changed: 43 additions & 75 deletions
Original file line numberDiff line numberDiff line change
@@ -37,86 +37,54 @@ opt_custom_params:
3737
opt_security_opt_param: true
3838
opt_security_opt_param_vars:
3939
- {run_var: "seccomp=unconfined", compose_var: "seccomp:unconfined", desc: "For Docker Engine only, many modern gui apps need this to function on older hosts as syscalls are unknown to Docker."}
40-
opt_param_device_map: true
41-
opt_param_devices:
42-
- {device_path: "/dev/dri", device_host_path: "/dev/dri", desc: "Add this for GL support (Linux hosts only)"}
43-
# Kasm blurb settings
44-
kasm_blurb: true
45-
show_nvidia: true
46-
external_http_port: "3000"
47-
external_https_port: "3001"
48-
noto_fonts: "fonts-noto-cjk"
4940
# application setup block
5041
app_setup_block_enabled: true
5142
app_setup_block: |
52-
The Kali Linux image can be accessed at:
43+
The application can be accessed at:
5344
54-
* http://yourhost:3000/
5545
* https://yourhost:3001/
56-
# init diagram
57-
init_diagram: |
58-
"kali-linux:latest": {
59-
docker-mods
60-
base {
61-
fix-attr +\nlegacy cont-init
62-
}
63-
docker-mods -> base
64-
legacy-services
65-
custom services
66-
init-services -> legacy-services
67-
init-services -> custom services
68-
custom services -> legacy-services
69-
legacy-services -> ci-service-check
70-
init-migrations -> init-adduser
71-
init-kasmvnc-end -> init-config
72-
init-os-end -> init-config
73-
init-config -> init-config-end
74-
init-os-end -> init-crontab-config
75-
init-mods-end -> init-custom-files
76-
init-adduser -> init-device-perms
77-
base -> init-envfile
78-
init-os-end -> init-kasmvnc
79-
init-nginx -> init-kasmvnc-config
80-
init-video -> init-kasmvnc-end
81-
base -> init-migrations
82-
base -> init-mods
83-
init-config-end -> init-mods
84-
init-mods -> init-mods-end
85-
init-mods-package-install -> init-mods-end
86-
init-mods -> init-mods-package-install
87-
init-kasmvnc -> init-nginx
88-
base -> init-os-end
89-
init-adduser -> init-os-end
90-
init-device-perms -> init-os-end
91-
init-envfile -> init-os-end
92-
init-migrations -> init-os-end
93-
init-custom-files -> init-services
94-
init-mods-end -> init-services
95-
init-kasmvnc-config -> init-video
96-
init-services -> svc-cron
97-
svc-cron -> legacy-services
98-
init-services -> svc-de
99-
svc-nginx -> svc-de
100-
svc-de -> legacy-services
101-
init-services -> svc-docker
102-
svc-de -> svc-docker
103-
svc-docker -> legacy-services
104-
init-services -> svc-kasmvnc
105-
svc-pulseaudio -> svc-kasmvnc
106-
svc-kasmvnc -> legacy-services
107-
init-services -> svc-kclient
108-
svc-kasmvnc -> svc-kclient
109-
svc-kclient -> legacy-services
110-
init-services -> svc-nginx
111-
svc-kclient -> svc-nginx
112-
svc-nginx -> legacy-services
113-
init-services -> svc-pulseaudio
114-
svc-pulseaudio -> legacy-services
115-
}
116-
Base Images: {
117-
"baseimage-kasmvnc:kali" <- "baseimage-debian:kali"
118-
}
119-
"kali-linux:latest" <- Base Images
46+
47+
48+
### Security
49+
50+
>[!WARNING]
51+
>Do not put this on the Internet if you do not know what you are doing.
52+
53+
By default this container has no authentication and the optional environment variables `CUSTOM_USER` and `PASSWORD` to enable basic http auth via the embedded NGINX server should only be used to locally secure the container from unwanted access on a local network. If exposing this to the Internet we recommend putting it behind a reverse proxy, such as [SWAG](https://github.com/linuxserver/docker-swag), and ensuring a secure authentication solution is in place. From the web interface a terminal can be launched and it is configured for passwordless sudo, so anyone with access to it can install and run whatever they want along with probing your local network.
54+
55+
### Nvidia GPU Support
56+
57+
**Nvidia support is not compatible with Alpine based images as Alpine lacks Nvidia drivers**
58+
59+
Nvidia support is available by leveraging Zink for OpenGL support. This can be enabled with the following run flags:
60+
61+
| Variable | Description |
62+
| :----: | --- |
63+
| --gpus all | This can be filtered down but for most setups this will pass the one Nvidia GPU on the system |
64+
| --runtime nvidia | Specify the Nvidia runtime which mounts drivers and tools in from the host |
65+
66+
The compose syntax is slightly different for this as you will need to set nvidia as the default runtime:
67+
68+
```
69+
sudo nvidia-ctk runtime configure --runtime=docker --set-as-default
70+
sudo service docker restart
71+
```
72+
73+
And to assign the GPU in compose:
74+
75+
```
76+
services:
77+
webtop:
78+
image: lscr.io/linuxserver/suyu:latest
79+
deploy:
80+
resources:
81+
reservations:
82+
devices:
83+
- driver: nvidia
84+
count: 1
85+
capabilities: [compute,video,graphics,utility]
86+
```
87+
12088
# changelog
12189
changelogs:
12290
- {date: "19.06.25:", desc: "Rebase to Selkies baseimage."}

0 commit comments

Comments
 (0)