Docker · Setup · Server · 12 min read · October 8, 2026

Running Plex in Docker: Setup, Permissions, GPU Passthrough, and Updates

Why Docker for Plex?

Running Plex in Docker isolates it from your host OS, makes updates trivial, simplifies backups, and lets you reproduce your setup on any machine. It's the standard deployment method for anyone running Plex on Linux.

Docker Compose Setup

The official Plex Docker image is plexinc/pms-docker. Here's a production-ready compose file:

services:
  plex:
    image: plexinc/pms-docker:latest
    container_name: plex
    network_mode: host
    environment:
      - PLEX_CLAIM=claim-xxxx  # Get from plex.tv/claim
      - PLEX_UID=1000
      - PLEX_GID=1000
      - TZ=America/New_York
    volumes:
      - /opt/plex/config:/config
      - /opt/plex/transcode:/transcode
      - /mnt/media:/data:ro
    restart: unless-stopped

Key configuration choices

• network_mode: host — Required for DLNA, local network discovery, and simplest remote access. Bridge mode works but requires explicit port mapping and breaks some features
• PLEX_CLAIM — One-time token from plex.tv/claim that links the container to your account. Expires in 4 minutes, so have it ready before starting
• Transcode volume — Use an SSD or tmpfs for the transcode directory. Transcoding to a spinning disk causes stuttering during seeks
• Media as read-only — The :ro flag prevents Plex from accidentally modifying your media files

Volume Mounts and Permissions

The most common Docker Plex problem is permissions. The Plex process inside the container runs as the UID/GID you specify. Those IDs must have:

• Read access to your media directories
• Read/write access to the config directory
• Read/write access to the transcode directory

On the host, set ownership: chown -R 1000:1000 /opt/plex and ensure media files are readable by UID 1000.

GPU Passthrough in Docker

NVIDIA

Install the NVIDIA Container Toolkit, then add to your compose file:

deploy:
  resources:
    reservations:
      devices:
        - driver: nvidia
          count: 1
          capabilities: [gpu]

Intel Quick Sync

Pass the DRI device:

devices:
  - /dev/dri:/dev/dri

Verify inside the container: docker exec plex ls -la /dev/dri/ should show renderD128.

Automatic Updates

Use Watchtower to auto-update your Plex container:

services:
  watchtower:
    image: containrrr/watchtower
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - WATCHTOWER_CLEANUP=true
      - WATCHTOWER_SCHEDULE=0 0 4 * * *  # Check at 4 AM
    restart: unless-stopped

Watchtower checks for new images daily and recreates the container with the same settings. Your config persists because it's on a volume.

Backup Strategy

Your Plex config directory contains everything: database, metadata, posters, watch history, settings. Back it up regularly:

1. Stop the container: docker compose stop plex
2. Archive the config: tar -czf plex-backup-$(date +%F).tar.gz /opt/plex/config
3. Restart: docker compose start plex
4. Copy the backup offsite (rclone to cloud, rsync to NAS)

Common Pitfalls

• Using bridge networking: Breaks local network discovery and DLNA. Use host networking unless you have a specific reason not to
• Storing transcode on slow storage: Transcode files need fast random I/O. Use SSD, tmpfs, or a ramdisk
• Not setting timezone: Scheduled tasks (library scans, optimization) run at wrong times
• Claim token expired: If you didn't claim in time, delete the config directory and start fresh with a new token