2024-01-08, 05:45 PM
Thanks again for the explanation. It makes sense.
I actually asked a colleague who's got a very similar setup and he had a stroke of genius saying it's most likely the network mode of the container that needs to be host and not the default bridge... something to do with multicast and rtp protocol support (I do not have the full explanation but will look it up.... eventually).
So below is my docker compose for the jellyfin container that ended up enabling the streaming of the channels listed here (Swiss providers).
Thanks for the help, and my apologies if that bit of the network_mode was obvious and that I missed it when reading the doc.
I actually asked a colleague who's got a very similar setup and he had a stroke of genius saying it's most likely the network mode of the container that needs to be host and not the default bridge... something to do with multicast and rtp protocol support (I do not have the full explanation but will look it up.... eventually).
So below is my docker compose for the jellyfin container that ended up enabling the streaming of the channels listed here (Swiss providers).
Thanks for the help, and my apologies if that bit of the network_mode was obvious and that I missed it when reading the doc.
Code:
version: "3.8"
services:
jellyfin:
image: lscr.io/linuxserver/jellyfin:latest
network_mode: host
container_name: jellyfin
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Zurich
volumes:
- jellyfin:/config
- /mnt/Videos/TV:/data/tv
- /mnt/Videos/Movies:/data/movies
ports:
- 8096:8096
restart: unless-stopped
devices:
- "/dev/dri:/dev/dri"
volumes:
jellyfin:
external: true