I have a mini PC running Ubuntu. I use docker portainer to house Plex and all of the arrs services.

Due to playback issues which I assumed were due to EAC3 audio (a common issue which others reported), I removed Plex from docker and installed it outside.

To my frustration I am still getting buffer problems, so I downloaded the log file. This appears to be reporting constant network notifications. I have copied an extract below.

I have an ethernet cable plugged into the PC and (when I was using Windows pre Ubuntu) I have reserved the IP address in the router for the MAC address for the ethernet adaptor.

I have no idea where to start in troubleshooting this. Is the WIFI adapter trying to connect? Or is the docker network interfering? I have no experience with this so would be very grateful for some pointers.

Aug 20, 2024 22:11:13.719 [135727832640312] DEBUG - NetworkInterface: received Netlink message len=88, type=RTM_DELADDR, flags=0x0 Aug 20, 2024 22:11:13.719 [135727832640312] DEBUG - NetworkInterface: Netlink address message family=2, index=3, flags=0x0 Aug 20, 2024 22:11:13.719 [135727832640312] DEBUG - Network change. Aug 20, 2024 22:11:13.719 [135727832640312] DEBUG - NetworkInterface: Notified of network changed (force=0) Aug 20, 2024 22:11:13.720 [135727832640312] DEBUG - Network change notification but nothing changed.

  • pnutzh4x0rA
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    This reddit post seems relevant. A user mentions:

    I found out that only the containers having these kind of networking problems where all running the container in “host” networking mode.https://docs.docker.com/network/drivers/

    Since I don’t need host mode, I can just comment that line out, and it will start using the standard Bridge (which will be used by default if you don’t specify any networking settings for your containers)

    This is running under docker as you had in your initial configuration.

    Another reddit post mentions setting the gateway and DNS server if you have a static IP:

    It turned out to be nothing to do with Plex but rather was the fact that there was missing information on my static IP setup. Once I added in the gateway and DNS information those extraneous messages went away.

    I’m not sure if that will help, but it’s perhaps something you could consider as you debug this issue. Good luck.

    • assassin6@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      Thanks for your insights.

      The router is set up to give the PC a static IP already. I have now gone into the Networks page in Ubuntu desktop, set the IPv4 method from Automatic DHCP to Manual, and added my static IP there.

      The arrs and other docker containers all use the same bridge network (and not the default network). None except for Plex are set to use Host.

      I have removed Plex again and added it once more to the docker. Unfortunately Plex logs are still showing the same issue.