https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/linuxserver_medium.png]([***]
The LinuxServer.io team brings you another container release featuring:
Find us at:
 VERSION IF YOU ARE NOT LOGGED IN WITH A PLEXPASS ACCOUNT.
docker: Let Docker handle the Plex Version, we keep our Dockerhub Endpoint up to date with the latest public builds. This is the same as leaving this setting out of your create command.latest: will update plex to the latest version available that you are entitled to.public: will update plexpass users to the latest public version, useful for plexpass users that don't want to be on the bleeding edge but still want the latest public updates.<specific-version>: will select a specific version (eg 0.9.12.4.1192-9a47d21) of plex to install, note you cannot use this to access plexpass versions if you do not have plexpass.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.
Intel/ATI/AMD
To leverage hardware acceleration you will need to mount /dev/dri video device inside of 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.
Nvidia
Hardware acceleration users for Nvidia will need to install the container runtime provided by Nvidia on their host, instructions can be found here: https://github.com/NVIDIA/nvidia-container-toolkit
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.
Arm Devices
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.
This image can be run with a read-only container filesystem. For details please read the docs.
This image can be run with a non-root user. For details please read the docs.
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
[!NOTE] Unless a parameter is flagged as 'optional', it is mandatory and a value must be provided.
yaml--- services: plex: image: lscr.io/linuxserver/plex:latest container_name: plex network_mode: host environment: - PUID=1000 - PGID=1000 - TZ=Etc/UTC - VERSION=docker - PLEX_CLAIM= #optional volumes: - /path/to/plex/library:/config - /path/to/tvseries:/tv - /path/to/movies:/movies restart: unless-stopped
bashdocker run -d \ --name=plex \ --net=host \ -e PUID=1000 \ -e PGID=1000 \ -e TZ=Etc/UTC \ -e VERSION=docker \ -e PLEX_CLAIM= `#optional` \ -v /path/to/plex/library:/config \ -v /path/to/tvseries:/tv \ -v /path/to/movies:/movies \ --restart unless-stopped \ lscr.io/linuxserver/plex:latest
Containers 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.
| Parameter | Function |
|---|---|
--net=host | Use Host Networking |
-e PUID=1000 | for UserID - see below for explanation |
-e PGID=1000 | for GroupID - see below for explanation |
-e TZ=Etc/UTC | specify a timezone to use, see this list. |
-e VERSION=docker | Set whether to update plex or not - see Application Setup section. |
-e PLEX_CLAIM= | Optionally you can obtain a claim token from [***] and input here. Keep in mind that the claim tokens expire within 4 minutes. |
-v /config | Plex library location. This can grow very large, 50gb+ is likely for a large collection. |
-v /tv | Media goes here. Add as many as needed e.g. /movies, /tv, etc. |
-v /movies | Media goes here. Add as many as needed e.g. /movies, /tv, etc. |
--read-only=true | Run container with a read-only filesystem. Please read the docs. |
--user=1000:1000 | Run container with a non-root user. Please read the docs. |
You can set any environment variable from a file by using a special prepend FILE__.
As an example:
bash-e FILE__MYVAR=/run/secrets/mysecretvariable
Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.
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 before asking for support.
If you want to run the container in bridge network mode (instead of the recommended host network mode) you will need to specify ports.
The official documentation for ports lists 32400 as the only required port.
The rest of the ports are optionally used for specific purposes listed in the documentation.
If you have not already claimed your server (first time setup) you need to set PLEX_CLAIM to claim a server set up with bridge networking.
-p 32400:32400 \ -p 1900:1900/udp \ -p 5353:5353/udp \ -p 8324:8324 \ -p 32410:32410/udp \ -p 32412:32412/udp \ -p 32413:32413/udp \ -p 32414:32414/udp \ -p 32469:32469
The application accepts a series of environment variables to further customize itself on boot:
| Parameter | Function |
|---|---|
--device=/dev/dri:/dev/dri | Add this option to your run command if you plan on using Quicksync hardware acceleration - see Application Setup section. |
--device=/dev/dvb:/dev/dvb | Add this option to your run command if you plan on using dvb devices. |
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 your_user as below:
bashid your_user
Example output:
textuid=1000(your_user) gid=1000(your_user) groups=1000(your_user)
https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=plex&query=%24.mods%5B%27plex%27%5D.mod_count&url=https%3A%2F%2Fraw.githubusercontent.com%2Flinuxserver%2Fdocker-mods%2Fmaster%2Fmod-list.yml]([] "view available mods for this container.") https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=universal&query=%24.mods%5B%27universal%27%5D.mod_count&url=https%3A%2F%2Fraw.githubusercontent.com%2Flinuxserver%2Fdocker-mods%2Fmaster%2Fmod-list.yml]([] "view available universal mods.")
We publish various https://github.com/linuxserver/docker-mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
Shell access whilst the container is running:
bashdocker exec -it plex /bin/bash
To monitor the logs of the container in realtime:
bashdocker logs -f plex
Container version number:
bashdocker inspect -f '{{ index .Config.Labels "build_version" }}' plex
Image version number:
bashdocker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/plex:latest
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
Update images:
All images:
bashdocker-compose pull
Single image:
bashdocker-compose pull plex
Update containers:
All containers:
bashdocker-compose up -d
Single container:
bashdocker-compose up -d plex
You can also remove the old dangling images:
bashdocker image prune
Update the image:
bashdocker pull lscr.io/linuxserver/plex:latest
Stop the running container:
bashdocker stop plex
Delete the container:
bashdocker rm plex
Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
You can also remove the old dangling images:
bashdocker image prune
[!TIP] We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
If you want to make local modifications to these images for development purposes or just to customize the logic:
bashgit clone https://github.com/linuxserver/docker-plex.git cd docker-plex docker build \ --no-cache \ --pull \ -t lscr.io/linuxserver/plex:latest .
The ARM variants can be built on x86_64 hardware and vice versa using lscr.io/linuxserver/qemu-static
bashdocker run --rm --privileged lscr.io/linuxserver/qemu-static --reset
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
UMASK_SET in favor of UMASK in baseimage, see above for more information./transcode volume mapping as it is now set via plex gui and defaults to a location under /config.VERSION=public./transcode volume support (upstream Plex change) and modified PlexPass download method to prevent unauthorised usage of paid PMS以下是 linuxserver/plex 相关的常用 Docker 镜像,适用于 不同场景 等不同场景:
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。




探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
无需登录使用专属域名
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
Harbor Proxy Repository 对接专属域名
Portainer Registries 加速拉取
Nexus3 Docker Proxy 内网缓存
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
docker search 限制
站内搜不到镜像
离线 save/load
插件要用 plugin install
WSL 拉取慢
安全与 digest
新手拉取配置
镜像合规机制
manifest unknown
no matching manifest(架构)
invalid tar header(解压)
TLS 证书失败
DNS 超时
域名连通性排查
410 Gone 排查
402 与流量用尽
401 认证失败
429 限流
D-Bus 凭证提示
413 与超大单层
来自真实用户的反馈,见证轩辕镜像的优质服务