专属域名
文档搜索
轩辕助手
Run助手
邀请有礼
返回顶部
快速返回页面顶部
收起
收起工具栏
轩辕镜像 官方专业版
轩辕镜像
专业版
轩辕镜像 官方专业版
轩辕镜像
专业版
首页个人中心搜索镜像

交易
充值流量我的订单
工具
提交工单镜像收录一键安装
Npm 源Pip 源Homebrew 源
帮助
常见问题轩辕镜像免费版
其他
关于我们网站地图
热门搜索:
plex

linuxserver/plex

自动构建
linuxserver

这是由LinuxServer.io为您提供的Plex Media Server容器,它是一款集成了Plex媒体服务器软件的轻量级、可移植Docker容器,能够帮助用户高效组织电影、音乐、照片等各类媒体文件,并支持跨设备流式传输与访问,适用于搭建个人或家庭媒体中心;LinuxServer.io作为专注开源容器开发的组织,致力于提供高质量、易于部署的容器镜像,此Plex Media Server容器便是其优质作品,为媒体管理与分享带来便捷体验。

2.1千 次收藏下载次数: 0状态:自动构建维护者:linuxserver仓库类型:镜像最近更新:15 天前
轩辕镜像,快一点,稳很多。点击查看
DockerHub 官方简介
轩辕镜像中文简介
标签下载
镜像标签列表与下载命令
轩辕镜像,快一点,稳很多。点击查看

https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/linuxserver_medium.png]([***]

The LinuxServer.io team brings you another container release featuring:

  • regular and timely application updates
  • easy user mappings (PGID, PUID)
  • custom base image with s6 overlay
  • weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
  • regular security updates

Find us at:

  • Blog - all the things you can do with our containers including How-To guides, opinions and much more!
  • *** - realtime support / chat with the community and the team.
  • Discourse - post on our community forum.
  • https://github.com/linuxserver - view the source for all of our repositories.
  • Open Collective - please *** helping us by either donating or contributing to our budget

https://github.com/linuxserver/docker-plex

![Scarf.io pulls]([] ![GitLab Container Registry]([] ![Quay.io]([] ![Jenkins Build]([] ![LSIO CI]([***]

Plex organizes video, music and photos from personal media libraries and streams them to smart TVs, streaming boxes and mobile devices. This container is packaged as a standalone Plex Media Server. Straightforward design and bulk actions mean getting things done faster.

https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/plex-logo.png]([***]

Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker https://distribution.github.io/distribution/spec/manifest-v2-2/#manifest-list and our announcement here.

Simply pulling lscr.io/linuxserver/plex:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

ArchitectureAvailableTag
x86-64✅amd64-<version tag>
arm64✅arm64v8-<version tag>

Application Setup

Webui can be found at <your-ip>:32400/web

[!NOTE] If there is no value set for the VERSION variable, then no updates will take place.

[!NOTE] For new users, no updates will take place on the first run of the container as there is no preferences file to read your token from, to update restart the Docker container after logging in through the webui.

Valid settings for VERSION are:-

[!NOTE] YOU CANNOT UPDATE TO A PLEXPASS ONLY (BETA) 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.

Hardware Acceleration

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.

Read-Only Operation

This image can be run with a read-only container filesystem. For details please read the docs.

Caveats

  • Runtime update of Plex (and thus Plexpass builds) is not supported.
  • Transcode directory must be mounted to a host path or tmpfs.

Non-Root Operation

This image can be run with a non-root user. For details please read the docs.

Caveats

  • Runtime update of Plex (and thus Plexpass builds) is not supported.
  • Transcode directory must be mounted to a host path or tmpfs.

Usage

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.

docker-compose (recommended, click here for more info)

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

docker cli (click here for more info)

bash
docker 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

Parameters

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.

ParameterFunction
--net=hostUse Host Networking
-e PUID=1000for UserID - see below for explanation
-e PGID=1000for GroupID - see below for explanation
-e TZ=Etc/UTCspecify a timezone to use, see this list.
-e VERSION=dockerSet 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 /configPlex library location. This can grow very large, 50gb+ is likely for a large collection.
-v /tvMedia goes here. Add as many as needed e.g. /movies, /tv, etc.
-v /moviesMedia goes here. Add as many as needed e.g. /movies, /tv, etc.
--read-only=trueRun container with a read-only filesystem. Please read the docs.
--user=1000:1000Run container with a non-root user. Please read the docs.

Environment variables from files (Docker secrets)

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.

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 before asking for support.

Optional Parameters

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:

ParameterFunction
--device=/dev/dri:/dev/driAdd this option to your run command if you plan on using Quicksync hardware acceleration - see Application Setup section.
--device=/dev/dvb:/dev/dvbAdd this option to your run command if you plan on using dvb devices.

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.

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:

bash
id your_user

Example output:

text
uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

Docker Mods

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.

Support Info

  • Shell access whilst the container is running:

    bash
    docker exec -it plex /bin/bash
    
  • To monitor the logs of the container in realtime:

    bash
    docker logs -f plex
    
  • Container version number:

    bash
    docker inspect -f '{{ index .Config.Labels "build_version" }}' plex
    
  • Image version number:

    bash
    docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/plex:latest
    

Updating Info

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:

Via Docker Compose

  • Update images:

    • All images:

      bash
      docker-compose pull
      
    • Single image:

      bash
      docker-compose pull plex
      
  • Update containers:

    • All containers:

      bash
      docker-compose up -d
      
    • Single container:

      bash
      docker-compose up -d plex
      
  • You can also remove the old dangling images:

    bash
    docker image prune
    

Via Docker Run

  • Update the image:

    bash
    docker pull lscr.io/linuxserver/plex:latest
    
  • Stop the running container:

    bash
    docker stop plex
    
  • Delete the container:

    bash
    docker 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:

    bash
    docker image prune
    

Image Update Notifications - Diun (Docker Image Update Notifier)

[!TIP] We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

Building locally

If you want to make local modifications to these images for development purposes or just to customize the logic:

bash
git 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

bash
docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 15.03.26: - Allow TMPDIR to be changed to better support read-only containers
  • 15.03.26: - Fix initial claim setup on non-root containers
  • 04.11.24: - Add Nvidia capability needed for h265
  • 18.07.24: - Rebase to Ubuntu Noble.
  • 12.02.24: - Use universal hardware acceleration blurb
  • 09.01.24: - Set ownership on TranscoderTempDirectory when it's been saved in Preferences.
  • 16.08.23: - Install unrar from https://github.com/linuxserver/docker-unrar.
  • 03.07.23: - Deprecate armhf. As announced here
  • 16.10.22: - Rebase to jammy. Update to s6v3. Remove opencl packages (bundled with plex).
  • 18.07.22: - Pin all opencl related driver packages.
  • 16.05.22: - Pin opencl version.
  • 04.03.22: - Increase verbosity of video device permissions fix, attempt to fix missing group rw.
  • 25.12.21: - Install Intel drivers from the official repo.
  • 20.01.21: - Deprecate UMASK_SET in favor of UMASK in baseimage, see above for more information.
  • 10.12.20: - Add latest Intel Compute packages from github repo for opencl support on latest gen igpu.
  • 23.11.20: - Add Bionic branch make Focal default.
  • 03.05.20: - Update exposed ports and example docs for bridge mode.
  • 23.03.20: - Remove udev hack (no longer needed), suppress uuid error in log during first start.
  • 04.12.19: - Add variable for setting PLEX_CLAIM. Remove /transcode volume mapping as it is now set via plex gui and defaults to a location under /config.
  • 06.08.19: - Add variable for setting UMASK.
  • 10.07.19: - Fix permissions for tuner (/dev/dvb) devices.
  • 20.05.19: - Bugfix do not allow Root group for Intel QuickSync ownership rules.
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 22.03.19: - Fix update logic for VERSION=public.
  • 14.03.19: - Switch to new api endpoints, enable beta (plex pass) updates for armhf and aarch64.
  • 15.02.19: - Clean up plex pid after unclean stop.
  • 11.02.19: - Fix nvidia variables, add device variables.
  • 16.01.19: - Add pipeline logic, multi arch, and HW transcoding configuration; remove avahi service.
  • 07.09.18: - Rebase to ubuntu bionic, add udev package.
  • 09.12.17: - Fix continuation lines.
  • 12.07.17: - Add inspect commands to README, move to jenkins build and push.
  • 28.05.17: - Add unrar package as per requests, for subzero plugin.
  • 11.01.17: - Use Plex environment variables from pms docker, change abc home folder to /app to alleviate usermod chowning library
  • 03.01.17: - Use case insensitive version variable matching rather than export and make lowercase.
  • 17.10.16: - Allow use of uppercase version variable
  • 01.10.16: - Add TZ info to README.
  • 09.09.16: - Add layer badges to README.
  • 27.08.16: - Add badges to README.
  • 22.08.16: - Rebased to xenial and s6 overlay
  • 07.04.16: - removed /transcode volume support (upstream Plex change) and modified PlexPass download method to prevent unauthorised usage of paid PMS
  • 24.09.15: - added optional support for volume transcoding (/transcode), and various typo fixes.
  • 17.09.15: - Changed to run chmod only once
  • 19.09.15: - Plex updated their download servers from http to https
  • 28.08.15: - Removed plexpass from routine, and now uses VERSION as a combination fix.
  • 18.07.15: - Moved autoupdate to be hosted by linuxserver.io and implemented bugfix thanks to ljm42.
  • 09.07.15: - Now with ability to pick static version number.
  • 08.07.15: - Now with autoupdates. (Hosted by fanart.tv)
  • 03.07.15: - Fixed a mistake that allowed plex to run as user plex rather than abc (99:100). Thanks to double16 for spotting this.

更多相关 Docker 镜像与资源

以下是 linuxserver/plex 相关的常用 Docker 镜像,适用于 不同场景 等不同场景:

  • nyanmisaka/jellyfin Docker 镜像说明(开源媒体服务器,支持多平台流媒体播放)
  • jellyfin/jellyfin Docker 镜像说明(Jellyfin 媒体服务器,开源流媒体平台,支持多平台播放)
  • emby/embyserver Docker 镜像说明(Emby 媒体服务器,开源流媒体平台,支持多平台播放和媒体管理)
  • linuxserver/jellyfin Docker 镜像说明(Jellyfin 媒体服务器,LinuxServer 维护版本)

镜像拉取方式

您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。

轩辕镜像加速拉取命令点我查看更多 plex 镜像标签

docker pull docker.xuanyuan.run/linuxserver/plex:<标签>

使用方法:

  • 登录认证方式
  • 免认证方式

DockerHub 原生拉取命令

docker pull linuxserver/plex:<标签>

更多 plex 镜像推荐

jaymoulin/plex logo

jaymoulin/plex

jaymoulin
这是一个支持多架构的Plex媒体服务器Docker容器,可适配树莓派等多种设备,能够集中管理音视频、图片等媒体文件,并通过网络向各类终端设备流式传输内容,借助Docker容器的轻量化特性实现便捷部署与跨平台运行,满足家庭或个人搭建私有媒体中心的需求,提供高效稳定的媒体管理与播放服务。
61 次收藏500万+ 次下载
17 天前更新
ghostserverd/plex logo

ghostserverd/plex

ghostserverd
围绕linuxserver/plex的配置包装器,用于简化其配置管理。
100万+ 次下载
16 天前更新
tianon/plex logo

tianon/plex

tianon
使用Plex Media Server在所有设备上享受您自己的媒体。
2 次收藏5万+ 次下载
17 天前更新
jonoh/plex logo

jonoh/plex

jonoh
官方Plex Docker镜像的非官方构建版本,除支持amd64架构外,还提供arm7和arm64架构支持,标签与官方镜像一致(包含Plex版本号),适合多架构环境使用,仅需amd64时建议使用官方镜像。
1 次收藏1万+ 次下载
1 个月前更新

查看更多 plex 相关镜像

轩辕镜像配置手册

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式

Docker 配置

登录仓库拉取

通过 Docker 登录认证访问私有仓库

专属域名拉取

无需登录使用专属域名

K8s Containerd

Kubernetes 集群配置 Containerd

K3s

K3s 轻量级 Kubernetes 镜像加速

Dev Containers

VS Code Dev Containers 配置

Podman

Podman 容器引擎配置

Singularity/Apptainer

HPC 科学计算容器配置

其他仓库配置

ghcr、Quay、nvcr 等镜像仓库

Harbor 镜像源配置

Harbor Proxy Repository 对接专属域名

Portainer 镜像源配置

Portainer Registries 加速拉取

Nexus 镜像源配置

Nexus3 Docker Proxy 内网缓存

系统配置

Linux

在 Linux 系统配置镜像服务

Windows/Mac

在 Docker Desktop 配置镜像

MacOS OrbStack

MacOS OrbStack 容器配置

Docker Compose

Docker Compose 项目配置

NAS 设备

群晖

Synology 群晖 NAS 配置

飞牛

飞牛 fnOS 系统配置镜像

绿联

绿联 NAS 系统配置镜像

威联通

QNAP 威联通 NAS 配置

极空间

极空间 NAS 系统配置服务

网络设备

爱快路由

爱快 iKuai 路由系统配置

宝塔面板

在宝塔面板一键配置镜像

需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单

镜像拉取常见问题

使用与功能问题

配置了专属域名后,docker search 为什么会报错?

docker search 限制

Docker Hub 上有的镜像,为什么在轩辕镜像网站搜不到?

站内搜不到镜像

机器不能直连外网时,怎么用 docker save / load 迁镜像?

离线 save/load

docker pull 拉插件报错(plugin v1+json)怎么办?

插件要用 plugin install

WSL 里 Docker 拉镜像特别慢,怎么排查和优化?

WSL 拉取慢

轩辕镜像安全吗?如何用 digest 校验镜像没被篡改?

安全与 digest

第一次用轩辕镜像拉 Docker 镜像,要怎么登录和配置?

新手拉取配置

轩辕镜像合规吗?轩辕镜像的合规是怎么做的?

镜像合规机制

错误码与失败问题

docker pull 提示 manifest unknown 怎么办?

manifest unknown

docker pull 提示 no matching manifest 怎么办?

no matching manifest(架构)

镜像已拉取完成,却提示 invalid tar header 或 failed to register layer 怎么办?

invalid tar header(解压)

Docker pull 时 HTTPS / TLS 证书验证失败怎么办?

TLS 证书失败

Docker pull 时 DNS 解析超时或连不上仓库怎么办?

DNS 超时

docker 无法连接轩辕镜像域名怎么办?

域名连通性排查

Docker 拉取出现 410 Gone 怎么办?

410 Gone 排查

出现 402 或「流量用尽」提示怎么办?

402 与流量用尽

Docker 拉取提示 UNAUTHORIZED(401)怎么办?

401 认证失败

遇到 429 Too Many Requests(请求太频繁)怎么办?

429 限流

docker login 提示 Cannot autolaunch D-Bus,还算登录成功吗?

D-Bus 凭证提示

为什么会出现「单层超过 20GB」或 413,无法加速拉取?

413 与超大单层

账号 / 计费 / 权限

轩辕镜像免费版和专业版有什么区别?

免费版与专业版区别

轩辕镜像支持哪些 Docker 镜像仓库?

支持的镜像仓库

镜像拉取失败还会不会扣流量?

失败是否计费

麒麟 V10 / 统信 UOS 提示 KYSEC 权限不够怎么办?

KYSEC 拦截脚本

如何在轩辕镜像申请开具发票?

申请开票

怎么修改轩辕镜像的网站登录和仓库登录密码?

修改登录密码

如何注销轩辕镜像账户?要注意什么?

注销账户

配置与原理类

写了 registry-mirrors,为什么还是走官方或仍然报错?

mirrors 不生效

怎么用 docker tag 去掉镜像名里的轩辕域名前缀?

去掉域名前缀

如何拉取指定 CPU 架构的镜像(如 ARM64、AMD64)?

指定架构拉取

用轩辕镜像拉镜像时快时慢,常见原因有哪些?

拉取速度原因

查看全部问题→

用户好评

来自真实用户的反馈,见证轩辕镜像的优质服务

用户头像

oldzhang

运维工程师

Linux服务器

5

"Docker访问体验非常流畅,大镜像也能快速完成下载。"

轩辕镜像
镜像详情
...
linuxserver/plex
博客Docker 镜像公告与技术博客
热门查看热门 Docker 镜像推荐
安装一键安装 Docker 并配置镜像源
镜像拉取问题咨询请 提交工单,官方技术交流群:1072982923。轩辕镜像所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
镜像拉取问题咨询请提交工单,官方技术交流群:。轩辕镜像所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
商务合作:点击复制邮箱
©2024-2026 源码跳动
商务合作:点击复制邮箱Copyright © 2024-2026 杭州源码跳动科技有限公司. All rights reserved.