Switch Networking Traefik docs for network_mode: "host" to match Traefik's docs using extra_hosts:

[rpatterson]

The Jellyfin docs for Traefik describe a configuration for network_mode: "host" that is different from and more complicated than what the Traefik docs describe. Specifically, it only requires adding an extra_hosts: hostname and requires no additional configuration file such as /srv/traefik-provider.toml.

I developed my Traefik configuration following the Traefik docs and only recently discovered the Jellyfin docs for Traefik, so I'm using the extra_hosts: approach and it works fine for me. Perhaps the Jellyfin docs for Traefik should be switched to that approach?

[rpatterson]

I'd be happy to submit a PR with changes to the Jellyfin Traefik docs if this change would be welcome. LMK.

[nielsvanvelzen]

Pull requests are always welcome!

[rpatterson]

Pull requests are always welcome!

Of course, but would this change in particular be preferred to the current docs, @nielsvanvelzen? I don't want to put the time into writing it up if it's not preferred for some reason and thus DOA.

[nielsvanvelzen]

Our documentation is mostly community maintained. I've never used Traefik myself so I can't say what is better.

[rpatterson]

In the hopes of saving others some time, after the recent upgrade to 10.9, Jellyfin changed the way it discovers which IP addresses to bind to which means it stopped binding to 172.17.0.1, I'm guessing because the docker0 bridge is state DOWN. Unfortunately, the Traefik docs use that IP in it's example and it's not entirely clear that users should use the real IP of the bridge for the specific network the Traefik container is running on:

# docker compose exec traefik ip route show src
default via 172.18.0.1 dev eth0

[rpatterson]

I've never used Traefik myself so I can't say what is better.

Right, so when someone else can say, LMK.