How do y’all manage all these Docker compose apps?

First I installed Jellyfin natively on Debian, which was nice because everything just worked with the normal package manager and systemd.

Then, Navidrome wasn’t in the repos, but it’s a simple Go binary and provides a systemd unit file, so that was not so bad just downloading a new binary every now and then.

Then… Immich came… and forced me to use Docker compose… :|

Now I’m looking at Frigate… and it also requires Docker compose… :|

Looking through the docs, looks like Jellyfin, Navidrome, Immich, and Frigate all require/support Docker compose…

At this point, I’m wondering if I should switch everything to Docker compose so I can keep everything straight.

But, how do folks manage this mess? Is there an analogue to apt update, apt upgrade, systemctl restart, journalctl for all these Docker compose apps? Or do I have to individually manage each app? I guess I could write a bash script… but… is this what other people do?

  • tehWrapper@lemmy.worldEnglish
    51·
    1 day ago

    I have finally had to switch to using docker for several things I use to just install manually (ttrss being the main one). It sure feels dirty when i use to just apt update and know everything was updated.

    I can see the draw for docker but feel it’s way over used right now.

      • tehWrapper@lemmy.worldEnglish
        1·
        5 hours ago

        Docker pull lacks a lot of the automation apt has if your using multiple images, and needing to restart them.

        I’m an old man set in my ways… i see the benefit of docker and having set images, but also see so much waste having multi installs of the same thing for different docker images.

        • Jakeroxs@sh.itjust.worksEnglish
          1·
          10 minutes ago

          Idk most of the time I just dcpull dcup (aliases ftw)

          Ofc had some stuff break occasionally if there’s a breaking change but the same could happen through apt no?

          I prefer it to dependency hell personally lol