• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support General Questions Docker network_mode

     
    • 0 Vote(s) - 0 Average

    Docker network_mode

    host vs bridge
    _Nick
    Offline

    Junior Member

    Posts: 14
    Threads: 5
    Joined: 2025 Feb
    Reputation: 0
    Country:United Kingdom
    #1
    2025-04-06, 01:53 PM (This post was last modified: 2025-04-12, 06:54 PM by _Nick. Edited 9 times in total.)
    Hi all, 

    According to the Jellyfin Docker install docs (https://jellyfin.org/docs/general/instal...container/), bridge is the default Docker network mode, with host only required for DLNA (never used). However, the docker run and compose example templates use host mode, without explaining if it's performance-related.  In other words, no official recommendation is mentioned.

    I found this Docker network_mode comparison table on LoadForge:
    [Image: docker-network-modes.png]
    https://loadforge.com/guides/advanced-network-configuration-for-high-performance-docker-containers#:~:text=The%20host%20network%20driver%20provides,network%20throughput%20and%20low%20latency

    Has anyone already benchmarked these differences specifically for Jellyfin workloads?  When direct-streaming large 4K HDR remuxes (65Mbps) over the internet (~20 miles), I frequently get micro-pauses/suttering. Could switching to a more secure/isolated mode like bridge worsen this?

    Thanks,

    P.S. I’m already considering pre-transcoding static HDR titles later down the line.


    Attached Files Thumbnail(s)
       
    Softw: Jellyfin 10.10.6, Docker, Ubuntu Server LTS
    Hardw: i5-7600K@5GHz, RTX 3080Ti, 64GB DDR4-3200, SATA SSD, 12TB Toshiba HDD (7200RPM 185MB/s)
    Users: 4 max concurrent (3 remote, 1 LAN, 1 remote 4K)
    Network: 1Gbps↓ / 115Mbps↑
    Media: Some 4K HDR remuxes
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2025-04-06, 03:29 PM
    In terms of performance and connection stability, the only issues I've seen from other users is when paired with a reverse proxy that is also in a container.  When your reverse proxy is also using bridge networking, you should not also publish port 8096 for Jellyfin.  This results in excessive "context switching" between the bridge network and the host network.  Not sure if that is that is the right term.

       

    But this is OK.

       

    If your reverse proxy is NOT a container, but runs directly on the host, the second image would result in pretty much the same thing.  But would require you use "expose" for port 8096, which is similar to port forwarding on your router.

    Code:
        expose:
          - 8096

    The idea is to reduce how many hops in and out of the bridge network your traffic makes.

    But, I've only seen the first image cause connection stability issues for some users.  I don't think there is a performance issue.  No additional CPU overhead or limited throughput.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    _Nick
    Offline

    Junior Member

    Posts: 14
    Threads: 5
    Joined: 2025 Feb
    Reputation: 0
    Country:United Kingdom
    #3
    2025-04-12, 06:53 PM (This post was last modified: 2025-04-12, 07:05 PM by _Nick. Edited 3 times in total.)
    Interesting. That makes perfect sense, thanks 🙂

    On the networking topic, this might help someone:
    I had stuttering and micro-pauses on my Sony KD-55XG9505 when streaming certain 4K HDR remuxes, even over LAN. Despite the £2000 price tag, Sony is still fitting 1990s era 100Mbps NICs. Much to my dismay, switching to WiFi resolved it instantly.
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode