Plex
Plex is a powerful media server that organizes your personal media libraries โ movies, TV shows, music, photos, and more โ and streams them to any device. This stack uses the LinuxServer.io Plex image, which provides a well-maintained container with regular updates and sensible defaults. Plex automatically fetches metadata, artwork, and descriptions for your media, organizes collections, and provides personalized recommendations. It supports hardware-accelerated transcoding, multi-user accounts with managed sharing, offline sync (with Plex Pass), and live TV with DVR support. Separate volumes are configured for server configuration, transcoding cache, and media files. After deployment, access the web UI on port 32400/web to sign in with your Plex account and claim the server. Set PLEX_CLAIM from https://plex.tv/claim for automatic server claiming.
Included Services
plex
lscr.io/linuxserver/plex:latest
Environment Variables:
Generated YAML
# Generated by ComposeHub (composehub.dev)
name: plex
services:
plex:
image: lscr.io/linuxserver/plex:latest
restart: always
ports:
- 32400:32400
volumes:
- plex_config:/config
- plex_transcode:/transcode
- plex_media:/data/media
environment:
PUID: ${PUID:-1000}
PGID: ${PGID:-1000}
TZ: ${TZ:-UTC}
VERSION: ${VERSION:-docker}
PLEX_CLAIM: ${PLEX_CLAIM:-}
networks:
- plex
healthcheck:
test:
- CMD-SHELL
- curl -f http://localhost:32400/identity || exit 1
interval: 30s
timeout: 10s
retries: 5
start_period: 45s
deploy:
resources:
limits:
cpus: "4.00"
memory: 2048M
reservations:
cpus: "0.50"
memory: 512M
labels:
com.composehub.description: Plex Media Server for streaming your personal media library
networks:
plex:
driver: bridge
volumes:
plex_config:
driver: local
plex_transcode:
driver: local
plex_media:
driver: local
Quick Info
- Services
- 1
- Networks
- 1
- Volumes
- 3
When to Use
This template is ideal for setting up a plex environment. All services are pre-configured with healthchecks, resource limits, and sensible defaults. Customize environment variables before deploying to production.
Tips
- Change all default passwords before deploying
- Review resource limits for your hardware
- Add a reverse proxy for production HTTPS
- Configure backup strategies for data volumes