2024-08-29, 07:32 PM 
		
	
	
		Do you have any reason to use the linuxserver image instead of the official image?
I spun up a linuxserver image, also saw the same "fontconfig" messages, but mine started anyway.
If you're ok with it, let's give the official image a try? You'd need to adjust your docker compose a little bit.
Before you start up the new container, backup your current jellyfin-config folder and then clear it out and clean up your old images.
Now start the jellyfin container.
	  
	
	
I spun up a linuxserver image, also saw the same "fontconfig" messages, but mine started anyway.
If you're ok with it, let's give the official image a try? You'd need to adjust your docker compose a little bit.
Code:
version: '3.9'
services:
  jellyfin:
    image: jellyfin/jellyfin:latest
    container_name: jellyfin
    user: 1000:1000
    environment:
      - TZ=America/New_York
      - JELLYFIN_PublishedServerUrl=10.11.12.5 #optional
    volumes:
      - /mnt/gfs2/ezarr/config/jellyfin-config/config:/config
      - /mnt/gfs2/ezarr/config/jellyfin-config/cache:/cache
      - /mnt/omen/video/data:/data
    ports:
      - 8096:8096
      - 8920:8920 #optional
      - 7359:7359/udp #optional
      - 1900:1900/udp #optional
    restart: unless-stoppedBefore you start up the new container, backup your current jellyfin-config folder and then clear it out and clean up your old images.
Code:
cp -pR /mnt/gfs2/ezarr/config/jellyfin-config /mnt/gfs2/ezarr/config/jellyfin-config-lsio
rm -rf /mnt/gfs2/ezarr/config/jellyfin-config/*Now start the jellyfin container.

