You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/images/docker-kdenlive.md
+95-82Lines changed: 95 additions & 82 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ The architectures supported by this image are:
34
34
| Architecture | Available | Tag |
35
35
| :----: | :----: | ---- |
36
36
| x86-64 | ✅ | amd64-\<version tag\>|
37
-
| arm64 |✅ | arm64v8-\<version tag\>|
37
+
| arm64 |❌ ||
38
38
39
39
## Application Setup
40
40
@@ -43,61 +43,73 @@ The application can be accessed at:
43
43
*http://yourhost:3000/
44
44
*https://yourhost:3001/
45
45
46
-
**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**
46
+
### Strict reverse proxies
47
+
48
+
This image uses a self-signed certificate by default. This naturally means the scheme is `https`.
49
+
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).
50
+
51
+
**Modern GUI desktop apps may have compatibility issues with the latest Docker syscall restrictions. You can use Docker with the `--security-opt seccomp=unconfined` setting to allow these syscalls on hosts with older Kernels or libseccomp versions.**
47
52
48
53
### Security
49
54
50
55
!!! warning
51
56
52
-
Do not put this on the Internet if you do not know what you are doing.
57
+
This container provides privileged access to the host system. Do not expose it to the Internet unless you have secured it properly.
53
58
54
-
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.
59
+
**HTTPS is required for full functionality.** Modern browser features such as WebCodecs, used for video and audio, will not function over an insecure HTTP connection.
55
60
56
-
### Options in all KasmVNC based GUI containers
61
+
By default, this container has no authentication. The optional `CUSTOM_USER` and `PASSWORD` environment variables enable basic HTTP auth, which is suitable only for securing the container on a trusted local network. For internet exposure, we strongly recommend placing the container behind a reverse proxy, such as [SWAG](https://github.com/linuxserver/docker-swag), with a robust authentication mechanism.
57
62
58
-
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.
63
+
The web interface includes a terminal with passwordless `sudo` access. Any user with access to the GUI can gain root control within the container, install arbitrary software, and probe your local network.
59
64
60
-
#### Optional environment variables
65
+
###Options in all Selkies-based GUI containers
61
66
62
-
| Variable | Description |
63
-
| :----: | --- |
64
-
| CUSTOM_PORT | Internal port the container listens on for http if it needs to be swapped from the default 3000. |
65
-
| CUSTOM_HTTPS_PORT | Internal port the container listens on for https if it needs to be swapped from the default 3001. |
| PASSWORD | HTTP Basic auth password, abc is default. If unset there will be no auth |
68
-
| SUBFOLDER | Subfolder for the application if running a subfolder reverse proxy, need both slashes IE `/subfolder/`|
69
-
| TITLE | The page title displayed on the web browser, default "KasmVNC Client". |
70
-
| FM_HOME | This is the home directory (landing) for the file manager, default "/config". |
71
-
| START_DOCKER | If set to false a container with privilege will not automatically start the DinD Docker setup. |
72
-
| 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`|
73
-
| DISABLE_IPV6 | If set to true or any value this will disable IPv6 |
74
-
| LC_ALL | Set the Language for the container to run as IE `fr_FR.UTF-8``ar_AE.UTF-8`|
75
-
| NO_DECOR | If set the application will run without window borders in openbox for use as a PWA. |
76
-
| NO_FULL | Do not autmatically fullscreen applications when using openbox. |
77
-
78
-
#### Optional run configurations
67
+
This container is based on [Docker Baseimage Selkies](https://github.com/linuxserver/docker-baseimage-selkies), which provides the following environment variables and run configurations to customize its functionality.
68
+
69
+
#### Optional Environment Variables
79
70
80
71
| Variable | Description |
81
72
| :----: | --- |
82
-
|`--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`. |
83
-
|`-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. |
73
+
|`CUSTOM_PORT`| Internal HTTP port. Defaults to `3000`. |
74
+
|`CUSTOM_HTTPS_PORT`| Internal HTTPS port. Defaults to `3001`. |
75
+
|`CUSTOM_USER`| Username for HTTP Basic Auth. Defaults to `abc`. |
76
+
|`PASSWORD`| Password for HTTP Basic Auth. If unset, authentication is disabled. |
77
+
|`SUBFOLDER`| Application subfolder for reverse proxy configurations. Must include leading and trailing slashes, e.g., `/subfolder/`. |
78
+
|`TITLE`| Page title displayed in the web browser. Defaults to "Selkies". |
79
+
|`START_DOCKER`| If set to `false`, the privileged Docker-in-Docker setup will not start automatically. |
80
+
|`DISABLE_IPV6`| Set to `true` to disable IPv6 support in the container. |
81
+
|`LC_ALL`| Sets the container's locale, e.g., `fr_FR.UTF-8`. |
82
+
|`DRINODE`| If mounting in /dev/dri for DRI3 GPU Acceleration allows you to specify the device to use IE `/dev/dri/renderD128`|
83
+
|`NO_DECOR`| If set, applications will run without window borders, suitable for PWA usage. |
84
+
|`NO_FULL`| If set, applications will not be automatically fullscreened. |
85
+
|`DISABLE_ZINK`| If set, Zink-related environment variables will not be configured when a video card is detected. |
86
+
|`WATERMARK_PNG`| Full path to a watermark PNG file inside the container, e.g., `/usr/share/selkies/www/icon.png`. |
|`--privileged`| Starts a Docker-in-Docker (DinD) environment. For better performance, mount the Docker data directory from the host, e.g., `-v /path/to/docker-data:/var/lib/docker`. |
94
+
|`-v /var/run/docker.sock:/var/run/docker.sock`| Mounts the host's Docker socket to manage host containers from within this container. |
84
95
|`--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) |
85
96
86
97
### Language Support - Internationalization
87
98
88
-
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.
89
-
90
-
To install cjk fonts on startup as an example pass the environment variables (Alpine base):
To launch the desktop session in a different language, set the `LC_ALL` environment variable. For example:
97
100
98
-
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.
The `DRINODE` environment variable can be used to point to a specific GPU.
115
-
Up to date information can be found [here](https://www.kasmweb.com/kasmvnc/docs/master/gpu_acceleration.html)
116
127
117
-
### Nvidia GPU Support (KasmVNC interface)
128
+
DRI3 will work on aarch64 given the correct drivers are installed inside the container for your chipset.
118
129
119
-
**Nvidia support is not compatible with Alpine based images as Alpine lacks Nvidia drivers**
130
+
### Nvidia GPU Support
120
131
121
-
Nvidia support is available by leveraging Zink for OpenGL support. This can be enabled with the following run flags:
132
+
**Note: Nvidia support is not available for Alpine-based images.**
122
133
123
-
| Variable | Description |
134
+
Nvidia GPU support is available by leveraging Zink for OpenGL. When a compatible Nvidia GPU is passed through, it will also be **automatically utilized for hardware-accelerated video stream encoding** (using the `x264enc` full-frame profile), significantly reducing CPU load.
135
+
136
+
Enable Nvidia support with the following runtime flags:
137
+
138
+
| Flag | Description |
124
139
| :----: | --- |
125
-
| --gpus all |This can be filtered down but for most setups this will pass the one Nvidia GPU on the system|
126
-
| --runtime nvidia |Specify the Nvidia runtime which mounts drivers and tools in from the host |
140
+
|`--gpus all`|Passes all available host GPUs to the container. This can be filtered to specific GPUs.|
141
+
|`--runtime nvidia`|Specifies the Nvidia runtime, which provides the necessary drivers and tools from the host.|
127
142
128
-
The compose syntax is slightly different for this as you will need to set nvidia as the default runtime:
143
+
For Docker Compose, you must first configure the Nvidia runtime as the default on the host:
Then, assign the GPU to the service in your `compose.yaml`:
136
151
137
152
```
138
153
services:
@@ -147,27 +162,32 @@ services:
147
162
capabilities: [compute,video,graphics,utility]
148
163
```
149
164
150
-
### Application management
165
+
### Application Management
166
+
167
+
There are two methods for installing applications inside the container: PRoot Apps (recommended for persistence) and Native Apps.
168
+
169
+
#### PRoot Apps (Persistent)
151
170
152
-
#### PRoot Apps
171
+
Natively installed packages (e.g., via `apt-get install`) will not persist if the container is recreated. To retain applications and their settings across container updates, we recommend using [proot-apps](https://github.com/linuxserver/proot-apps). These are portable applications installed to the user's persistent `$HOME` directory.
153
172
154
-
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:
173
+
To install an application, use the command line inside the container:
155
174
156
175
```
157
176
proot-apps install filezilla
158
177
```
159
178
160
-
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).
179
+
A list of supported applications is available [here](https://github.com/linuxserver/proot-apps?tab=readme-ov-file#supported-apps).
161
180
162
-
#### Native Apps
181
+
#### Native Apps (Non-Persistent)
163
182
164
-
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.
183
+
You can install packages from the system's native repository using the [universal-package-install](https://github.com/linuxserver/docker-mods/tree/universal-package-install) mod. This method will increase the container's start time and is not persistent. Add the following to your `compose.yaml`:
0 commit comments