clion007/jellyfin repository overview

The Free Software Media System

Jellyfin is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support. There are no strings attached, no premium licenses or features, and no hidden agendas: just a team who want to build something better and work together to achieve it.

This clion/jellyfin docker image provides a better alternative to the official Jellyfin container. It's built on the latest Alpine Linux, offering a smaller footprint while fixing FFmpeg decoding issues, hardware acceleration support, and Chinese character display problems. The image automatically updates when new Jellyfin versions are released.

⁠🚀 Application Setup

• WebUI can be accessed at http://<your-ip>:8096
• For detailed configuration options, please refer to the official Jellyfin documentation⁠

⁠🖥️ Hardware Acceleration

Hardware acceleration significantly improves transcoding performance. While not strictly required, it's highly recommended for optimal media streaming experience.

⁠For Intel/AMD/ATI GPUs:

Mount the /dev/dri device into the container:

--device=/dev/dri:/dev/dri

The container automatically configures proper permissions for the jellyfin user to access these devices.

⁠📋 Usage

You can deploy this container using either docker-compose (recommended) or the docker CLI.

⁠Docker Compose (Recommended)

services:
  jellyfin:
    container_name: Jellyfin
    image: clion007/jellyfin:latest
    environment:
      - UMASK=022
      - PUID=1000
      - PGID=1000
      - TZ=Asia/Shanghai
      - JELLYFIN_PublishedServerUrl=192.168.0.5 #optional
    ports:
      - 8096:8096
      - 8920:8920 #optional
      - 7359:7359/udp #optional
      - 1900:1900/udp #optional
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /path/to/jellyfin/library:/config
      - /path/to/media:/media/nas
    devices:
      - /dev/dri:/dev/dri #optional - for hardware transcoding
    restart: unless-stopped

⁠Docker CLI

docker run -d \
  --name=Jellyfin \
  -e UMASK=022 \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Asia/Shanghai \
  -e JELLYFIN_PublishedServerUrl=192.168.0.5 `#optional` \
  -p 8096:8096 \
  -p 8920:8920 `#optional` \
  -p 7359:7359/udp `#optional` \
  -p 1900:1900/udp `#optional` \
  -v /path/to/config:/config \
  -v /path/to/media:/media/nas \
  -v /etc/localtime:/etc/localtime:ro \
  --device=/dev/dri:/dev/dri `#optional - for hardware transcoding` \
  --restart unless-stopped \
  clion007/jellyfin:latest

⁠⚙️ Parameters

Containers are configured using parameters passed at runtime. 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.

⁠Port Mappings

⁠Environment Variables

⁠Volume Mappings

⁠Device Mappings

⁠🔧 Performance Tuning

For optimal performance with large media libraries:

1. Memory Allocation: Consider allocating sufficient memory:

   --memory=4g --memory-swap=6g
   

   Copy

2. Storage Performance: Mount configuration and media directories on high-performance storage

3. Network Configuration: For local streaming, consider using host networking:

   --network=host
   

   Copy

⁠🔐 Umask for Running Applications

This image provides the ability to override default permission settings using the optional -e UMASK=022 parameter. Remember that umask subtracts from permissions based on its value; it does not add permissions.

⁠👥 User / Group Identifiers

When using volumes, permission issues can arise between the host OS and the container. To avoid this, specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify, and permission issues will be resolved automatically.

⁠❓ Troubleshooting

⁠Transcoding Issues

• ✅ Verify hardware acceleration is properly configured;
• ✅ Check Jellyfin log for transcoding errors in your server, it should be in /path/to/config/log path;
• ✅ Ensure your jellyfin settings is right. The option "Prioritize fMP4-HLS Media Container" must not be selected. If your server's graphics card (GPU) is older and does not support H.264 Low-Power encoding, or H.265/AV1 encoding, you cannot select these encoding formats in the transcoding settings. The same applies to Hardware Acceleration options.

⁠Network Discovery Problems

• ✅ Confirm UDP ports 7359 and 1900 are properly mapped;
• ✅ Set the correct JELLYFIN_PublishedServerUrl environment variable.

⁠Permission Issues

• ✅ Verify PUID/PGID match the owner of your host directories;
• ✅ Check umask settings if files have incorrect permissions.