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
--label \"org.opencontainers.image.description=[Jellyfin](https://jellyfin.github.io/) is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support. There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it.\" \
524
+
--label \"org.opencontainers.image.description=[Jellyfin](https://github.com/jellyfin/jellyfin) is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support. There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it.\" \
--label \"org.opencontainers.image.description=[Jellyfin](https://jellyfin.github.io/) is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support. There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it.\" \
555
+
--label \"org.opencontainers.image.description=[Jellyfin](https://github.com/jellyfin/jellyfin) is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support. There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it.\" \
--label \"org.opencontainers.image.description=[Jellyfin](https://jellyfin.github.io/) is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support. There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it.\" \
583
+
--label \"org.opencontainers.image.description=[Jellyfin](https://github.com/jellyfin/jellyfin) is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support. There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it.\" \
[Jellyfin](https://jellyfin.github.io/) is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support. There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it.
42
+
[Jellyfin](https://github.com/jellyfin/jellyfin) is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support. There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it.
@@ -64,51 +64,70 @@ This image provides various versions that are available via tags. Please read th
64
64
| Tag | Available | Description |
65
65
| :----: | :----: |--- |
66
66
| latest | ✅ | Stable Jellyfin releases |
67
-
| nightly | ✅ |Unstable Jellyfin releases |
67
+
| nightly | ✅ |Nightly Jellyfin releases |
68
68
69
69
## Application Setup
70
70
71
71
Webui can be found at `http://<your-ip>:8096`
72
72
73
-
More information can be found in their official documentation [here](https://jellyfin.org/docs/general/quick-start.html).
73
+
More information can be found on the official documentation [here](https://jellyfin.org/docs/general/quick-start.html).
74
74
75
-
## Hardware Acceleration
75
+
###Hardware Acceleration Enhancements
76
76
77
-
### Intel
78
-
79
-
Hardware acceleration users for Intel Quicksync will need to mount their /dev/dri video device inside of the container by passing the following command when running or creating the container:
80
-
81
-
```--device=/dev/dri:/dev/dri```
82
-
83
-
We will automatically ensure the abc user inside of the container has the proper permissions to access this device.
77
+
This section lists the enhancements we have made for hardware acceleration in this image specifically.
84
78
85
-
### Nvidia
79
+
### Intel
86
80
87
-
Hardware acceleration users for Nvidia will need to install the container runtime provided by Nvidia on their host, instructions can be found here:
81
+
To enable the OpenCL based DV, HDR10 and HLG tone-mapping, please refer to the OpenCL-Intel mod from here:
88
82
89
-
https://github.com/NVIDIA/nvidia-docker
83
+
https://mods.linuxserver.io/?mod=jellyfin
90
84
91
-
We automatically add the necessary environment variable that will utilise all the features available on a GPU on the host. Once nvidia-docker is installed on your host you will need to re/create the docker container with the nvidia container runtime `--runtime=nvidia` and add an environment variable `-e NVIDIA_VISIBLE_DEVICES=all` (can also be set to a specific gpu's UUID, this can be discovered by running `nvidia-smi --query-gpu=gpu_name,gpu_uuid --format=csv` ). NVIDIA automatically mounts the GPU and drivers from your host into the jellyfin docker container.
92
85
93
-
###MMAL/OpenMAX (Raspberry Pi)
86
+
#### OpenMAX (Raspberry Pi)
94
87
95
-
Hardware acceleration users for Raspberry Pi MMAL/OpenMAX will need to mount their `/dev/vc-mem` and `/dev/vchiq` video devices inside of the container and their system OpenMax libs by passing the following options when running or creating the container:
88
+
Hardware acceleration users for Raspberry Pi MMAL/OpenMAX will need to mount their `/dev/vcsm` and `/dev/vchiq` video devices inside of the container and their system OpenMax libs by passing the following options when running or creating the container:
96
89
97
90
```
98
-
--device=/dev/vc-mem:/dev/vc-mem
91
+
--device=/dev/vcsm:/dev/vcsm
99
92
--device=/dev/vchiq:/dev/vchiq
100
93
-v /opt/vc/lib:/opt/vc/lib
101
94
```
102
95
103
-
### V4L2 (Raspberry Pi)
96
+
####V4L2 (Raspberry Pi)
104
97
105
98
Hardware acceleration users for Raspberry Pi V4L2 will need to mount their `/dev/video1X` devices inside of the container by passing the following options when running or creating the container:
99
+
106
100
```
107
101
--device=/dev/video10:/dev/video10
108
102
--device=/dev/video11:/dev/video11
109
103
--device=/dev/video12:/dev/video12
110
104
```
111
105
106
+
### Hardware Acceleration
107
+
108
+
Many desktop applications need access to a GPU to function properly and even some Desktop Environments have compositor effects that will not function without a GPU. However this is not a hard requirement and all base images will function without a video device mounted into the container.
109
+
110
+
#### Intel/ATI/AMD
111
+
112
+
To leverage hardware acceleration you will need to mount /dev/dri video device inside of the container.
113
+
114
+
```text
115
+
--device=/dev/dri:/dev/dri
116
+
```
117
+
118
+
We will automatically ensure the abc user inside of the container has the proper permissions to access this device.
119
+
120
+
#### Nvidia
121
+
122
+
Hardware acceleration users for Nvidia will need to install the container runtime provided by Nvidia on their host, instructions can be found here:
We automatically add the necessary environment variable that will utilise all the features available on a GPU on the host. Once nvidia-container-toolkit is installed on your host you will need to re/create the docker container with the nvidia container runtime `--runtime=nvidia` and add an environment variable `-e NVIDIA_VISIBLE_DEVICES=all` (can also be set to a specific gpu's UUID, this can be discovered by running `nvidia-smi --query-gpu=gpu_name,gpu_uuid --format=csv` ). NVIDIA automatically mounts the GPU and drivers from your host into the container.
126
+
127
+
#### Arm Devices
128
+
129
+
Best effort is made to install tools to allow mounting in /dev/dri on Arm devices. In most cases if /dev/dri exists on the host it should just work. If running a Raspberry Pi 4 be sure to enable `dtoverlay=vc4-fkms-v3d` in your usercfg.txt.
130
+
112
131
## Usage
113
132
114
133
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
@@ -174,20 +184,16 @@ Containers are configured using parameters passed at runtime (such as those abov
174
184
| Parameter | Function |
175
185
| :----: | --- |
176
186
|`-p 8096`| Http webUI. |
177
-
|`-p 8920`| Https webUI (you need to set up your own certificate). |
187
+
|`-p 8920`| Optional - Https webUI (you need to set up your own certificate). |
188
+
|`-p 7359/udp`| Optional - Allows clients to discover Jellyfin on the local network. |
189
+
|`-p 1900/udp`| Optional - Service discovery used by DNLA and clients. |
178
190
|`-e PUID=1000`| for UserID - see below for explanation |
179
191
|`-e PGID=1000`| for GroupID - see below for explanation |
180
192
|`-e TZ=Etc/UTC`| specify a timezone to use, see this [list](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List). |
193
+
|`-e JELLYFIN_PublishedServerUrl=192.168.0.5`| Set the autodiscovery response domain or IP address. |
181
194
|`-v /config`| Jellyfin data storage location. *This can grow very large, 50gb+ is likely for a large collection.*|
182
195
|`-v /data/tvshows`| Media goes here. Add as many as needed e.g. `/data/movies`, `/data/tv`, etc. |
183
196
|`-v /data/movies`| Media goes here. Add as many as needed e.g. `/data/movies`, `/data/tv`, etc. |
184
-
|`-v /opt/vc/lib`| Path for Raspberry Pi OpenMAX libs *optional*. |
185
-
|`--device /dev/dri`| Only needed if you want to use your Intel GPU for hardware accelerated video encoding (vaapi). |
186
-
|`--device /dev/vc-mem`| Only needed if you want to use your Raspberry Pi MMAL video decoding (Enabled as OpenMax H264 decode in gui settings). |
187
-
|`--device /dev/vchiq`| Only needed if you want to use your Raspberry Pi OpenMax video encoding (Bellagio). |
188
-
|`--device /dev/video10`| Only needed if you want to use your Raspberry Pi V4L2 video encoding. |
189
-
|`--device /dev/video11`| Only needed if you want to use your Raspberry Pi V4L2 video encoding. |
190
-
|`--device /dev/video12`| Only needed if you want to use your Raspberry Pi V4L2 video encoding. |
191
197
192
198
## Environment variables from files (Docker secrets)
193
199
@@ -206,6 +212,21 @@ Will set the environment variable `MYVAR` based on the contents of the `/run/sec
206
212
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.
207
213
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up [here](https://en.wikipedia.org/wiki/Umask) before asking for support.
208
214
215
+
## Optional Parameters
216
+
217
+
The [official documentation for ports](https://jellyfin.org/docs/general/networking/index.html) has additional ports that can provide auto discovery.
218
+
219
+
Service Discovery (`1900/udp`) - Since client auto-discover would break if this option were configurable, you cannot change this in the settings at this time. DLNA also uses this port and is required to be in the local subnet.
220
+
221
+
Client Discovery (`7359/udp`) - Allows clients to discover Jellyfin on the local network. A broadcast message to this port with "Who is Jellyfin Server?" will get a JSON response that includes the server address, ID, and name.
222
+
223
+
```
224
+
-p 7359:7359/udp \
225
+
-p 1900:1900/udp \
226
+
```
227
+
228
+
The [official documentation for environmentals](https://jellyfin.org/docs/general/administration/configuration.html) has additional environmentals that can provide additional configurability such as migrating to the native Jellyfin image.
229
+
209
230
## User / Group Identifiers
210
231
211
232
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`.
@@ -350,6 +371,7 @@ Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64
350
371
351
372
## Versions
352
373
374
+
***01.05.24:** - Increase verbosity of device permissions fixing. Use universal hardware acceleration blurb.
353
375
***03.12.23:** - Switch nightly to ffmpeg6.
354
376
***01.07.23:** - Deprecate armhf. As announced [here](https://www.linuxserver.io/blog/a-farewell-to-arm-hf)
355
377
***07.12.22:** - Rebase nightly to Jammy, migrate to s6v3.
0 commit comments