I’m trying to run Headphones via a Docker container on my Raspberry Pi 5, but things don’t seem to be going well. It’s like it brings the Pi down to its knees or something and all this despite the fact that it never appears to really start let alone finish the full scan. Anyone got any experience? Any tips? Anything I might’ve missed?

  • MajorHavoc@programming.devEnglish
    3·
    6 months ago

    I haven’t, personally, had good luck running Docker/podman on Raspberry Pi. I haven’t tried on a Pi 5, though.

    Previous Pi models didn’t seem to have enough mulicore power to get responsive docker/podman runs, for what I was trying.

    I don’t recall that I was trying anything too crazy, but arguably my baseline weekend project is a bit crazy, so your mileage may vary.

    It’s been awhile, but I feel like I ended up running Podman, instead of Docker, for some esoteric reason of my own. It was probably easier to build for the ARM processor.

    But again, it’s been awhile, and my memory is famously bad about these things.

    • jlow (he/him)@beehaw.orgEnglish
      5·
      6 months ago

      Mh, I ran multiple Docker containers on a 4 a few years ago (Jellyfin, Arrs, Syncthing, Portainer etc). It’s certainly possible, I didn’t notice it being that slow but switched to a NUC since because I a few things I wanted didn’t have ARM builds and other stuff.

    • sabreW4K3OPEnglish
      4·
      6 months ago

      Everything else I’m running on it runs fine, but Headphones is just being an oddball and it’s annoying. 😭

        • sabreW4K3OPEnglish
          3·
          6 months ago

          It’s definitely worth the investment. I’ve honestly got about 15 things running on mine, including Home Assistant, Jellyfin and Navidrome and it’s running idle at around 50% memory and 2% CPU.