kopia lustrzana https://github.com/linuxserver/docker-documentation
Bot Updating Documentation
LinuxServer-CI
rodzic
813439951c
commit
fa1bd12761
|
|
@ -1,6 +1,14 @@
|
|||
# linuxserver/emby
|
||||
# [linuxserver/emby](https://github.com/linuxserver/docker-emby)
|
||||
|
||||
[](https://github.com/linuxserver/docker-emby) [](https://github.com/linuxserver/docker-emby/releases) [](https://github.com/linuxserver/docker-emby/packages) [](https://gitlab.com/Linuxserver.io/docker-emby/container_registry) [](https://microbadger.com/images/linuxserver/emby) [](https://hub.docker.com/r/linuxserver/emby) [](https://hub.docker.com/r/linuxserver/emby) [](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-emby/job/master/) [](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/emby/latest/index.html)
|
||||
[](https://github.com/linuxserver/docker-emby)
|
||||
[](https://github.com/linuxserver/docker-emby/releases)
|
||||
[](https://github.com/linuxserver/docker-emby/packages)
|
||||
[](https://gitlab.com/Linuxserver.io/docker-emby/container_registry)
|
||||
[](https://microbadger.com/images/linuxserver/emby "Get your own version badge on microbadger.com")
|
||||
[](https://hub.docker.com/r/linuxserver/emby)
|
||||
[](https://hub.docker.com/r/linuxserver/emby)
|
||||
[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-emby/job/master/)
|
||||
[](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/emby/latest/index.html)
|
||||
|
||||
[Emby](https://emby.media/) organizes video, music, live TV, and photos from personal media libraries and streams them to smart TVs, streaming boxes and mobile devices. This container is packaged as a standalone emby Media Server.
|
||||
|
||||
|
|
@ -13,7 +21,7 @@ Simply pulling `linuxserver/emby` should retrieve the correct image for your arc
|
|||
The architectures supported by this image are:
|
||||
|
||||
| Architecture | Tag |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| x86-64 | amd64-latest |
|
||||
| arm64 | arm64v8-latest |
|
||||
| armhf | arm32v7-latest |
|
||||
|
|
@ -23,7 +31,7 @@ The architectures supported by this image are:
|
|||
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.
|
||||
|
||||
| Tag | Description |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| latest | Stable emby releases |
|
||||
| beta | Beta emby releases |
|
||||
|
||||
|
|
@ -33,7 +41,7 @@ Here are some example snippets to help you get started creating a container from
|
|||
|
||||
### docker
|
||||
|
||||
```text
|
||||
```
|
||||
docker create \
|
||||
--name=emby \
|
||||
-e PUID=1000 \
|
||||
|
|
@ -56,6 +64,7 @@ docker create \
|
|||
linuxserver/emby
|
||||
```
|
||||
|
||||
|
||||
### docker-compose
|
||||
|
||||
Compatible with docker-compose v2 schemas.
|
||||
|
|
@ -94,51 +103,52 @@ services:
|
|||
|
||||
## Parameters
|
||||
|
||||
Docker 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.
|
||||
Docker 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.
|
||||
|
||||
### Ports \(`-p`\)
|
||||
### Ports (`-p`)
|
||||
|
||||
| Parameter | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `8096` | Http webUI. |
|
||||
| `8920` | Https webUI \(you need to setup your own certificate\). |
|
||||
| `8920` | Https webUI (you need to setup your own certificate). |
|
||||
|
||||
### Environment Variables \(`-e`\)
|
||||
|
||||
### Environment Variables (`-e`)
|
||||
|
||||
| Env | Function |
|
||||
| :---: | :--- |
|
||||
| :----: | --- |
|
||||
| `PUID=1000` | for UserID - see below for explanation |
|
||||
| `PGID=1000` | for GroupID - see below for explanation |
|
||||
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London |
|
||||
| `UMASK_SET=<022>` | for umask setting of Emby, default if left unset is 022. |
|
||||
|
||||
### Volume Mappings \(`-v`\)
|
||||
### Volume Mappings (`-v`)
|
||||
|
||||
| Volume | Function |
|
||||
| :---: | :--- |
|
||||
| `/config` | Emby data storage location. _This can grow very large, 50gb+ is likely for a large collection._ |
|
||||
| :----: | --- |
|
||||
| `/config` | Emby data storage location. *This can grow very large, 50gb+ is likely for a large collection.* |
|
||||
| `/data/tvshows` | Media goes here. Add as many as needed e.g. `/data/movies`, `/data/tv`, etc. |
|
||||
| `/data/movies` | Media goes here. Add as many as needed e.g. `/data/movies`, `/data/tv`, etc. |
|
||||
| `/transcode` | Path for transcoding folder, _optional_. |
|
||||
| `/opt/vc/lib` | Path for Raspberry Pi OpenMAX libs _optional_. |
|
||||
|
||||
#### Device Mappings \(`--device`\)
|
||||
| `/transcode` | Path for transcoding folder, *optional*. |
|
||||
| `/opt/vc/lib` | Path for Raspberry Pi OpenMAX libs *optional*. |
|
||||
|
||||
#### Device Mappings (`--device`)
|
||||
| Parameter | Function |
|
||||
| :---: | :--- |
|
||||
| `/dev/dri` | Only needed if you want to use your Intel GPU for hardware accelerated video encoding \(vaapi\). |
|
||||
| `/dev/vchiq` | Only needed if you want to use your Raspberry Pi OpenMax video encoding \(Bellagio\). |
|
||||
| :-----: | --- |
|
||||
| `/dev/dri` | Only needed if you want to use your Intel GPU for hardware accelerated video encoding (vaapi). |
|
||||
| `/dev/vchiq` | Only needed if you want to use your Raspberry Pi OpenMax video encoding (Bellagio). |
|
||||
| `/dev/video10` | Only needed if you want to use your Raspberry Pi V4L2 video encoding. |
|
||||
| `/dev/video11` | Only needed if you want to use your Raspberry Pi V4L2 video encoding. |
|
||||
| `/dev/video12` | Only needed if you want to use your Raspberry Pi V4L2 video encoding. |
|
||||
|
||||
## Environment variables from files \(Docker secrets\)
|
||||
|
||||
## Environment variables from files (Docker secrets)
|
||||
|
||||
You can set any environment variable from a file by using a special prepend `FILE__`.
|
||||
|
||||
As an example:
|
||||
|
||||
```text
|
||||
```
|
||||
-e FILE__PASSWORD=/run/secrets/mysecretpassword
|
||||
```
|
||||
|
||||
|
|
@ -146,17 +156,19 @@ Will set the environment variable `PASSWORD` based on the contents of the `/run/
|
|||
|
||||
## Umask for running applications
|
||||
|
||||
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](https://en.wikipedia.org/wiki/Umask) before asking for support.
|
||||
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](https://en.wikipedia.org/wiki/Umask) before asking for support.
|
||||
|
||||
|
||||
## User / Group Identifiers
|
||||
|
||||
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`.
|
||||
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 user` as below:
|
||||
|
||||
```text
|
||||
```
|
||||
$ id username
|
||||
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
||||
```
|
||||
|
|
@ -169,7 +181,8 @@ Emby has very complete and verbose documentation located [here](https://github.c
|
|||
|
||||
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:
|
||||
|
||||
```text
|
||||
```--device=/dev/dri:/dev/dri```
|
||||
|
||||
We will automatically ensure the abc user inside of the container has the proper permissions to access this device.
|
||||
|
||||
Hardware acceleration users for Nvidia will need to install the container runtime provided by Nvidia on their host, instructions can be found here:
|
||||
|
|
@ -182,24 +195,25 @@ We automatically add the necessary environment variable that will utilise all th
|
|||
|
||||
Hardware acceleration users for Raspberry Pi OpenMAX will need to mount their /dev/vchiq video device inside of the container and their system OpenMax libs by passing the following options when running or creating the container:
|
||||
```
|
||||
--device=/dev/vchiq:/dev/vchiq
|
||||
-v /opt/vc/lib:/opt/vc/lib
|
||||
```
|
||||
|
||||
--device=/dev/vchiq:/dev/vchiq -v /opt/vc/lib:/opt/vc/lib
|
||||
|
||||
```text
|
||||
### V4L2 (Raspberry Pi)
|
||||
|
||||
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:
|
||||
```
|
||||
--device=/dev/video10:/dev/video10
|
||||
--device=/dev/video11:/dev/video11
|
||||
--device=/dev/video12:/dev/video12
|
||||
```
|
||||
|
||||
--device=/dev/video10:/dev/video10 --device=/dev/video11:/dev/video11 --device=/dev/video12:/dev/video12
|
||||
|
||||
\`\`\`
|
||||
|
||||
## Docker Mods
|
||||
[](https://mods.linuxserver.io/?mod=emby "view available mods for this container.")
|
||||
|
||||
[](https://mods.linuxserver.io/?mod=emby)
|
||||
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) can be accessed via the dynamic badge above.
|
||||
|
||||
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image \(if any\) can be accessed via the dynamic badge above.
|
||||
|
||||
## Support Info
|
||||
|
||||
|
|
@ -216,9 +230,8 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
|
|||
|
||||
* **29.02.20:** - Add v4l2 support on Raspberry Pi.
|
||||
* **26.02.20:** - Add openmax support on Raspberry Pi.
|
||||
* **15.02.20:** - Allow restarting emby from the gui \(also allows for auto restarts after addon updates\).
|
||||
* **15.02.20:** - Allow restarting emby from the gui (also allows for auto restarts after addon updates).
|
||||
* **02.10.19:** - Improve permission fixing for render and dvb devices.
|
||||
* **13.08.19:** - Add umask environment variable.
|
||||
* **24.06.19:** - Fix typos in readme.
|
||||
* **30.05.19:** - Initial release.
|
||||
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue