Should I be learning docker compose instead of relying on dockStarter to manage my containers? I got portainer up, should I just use that to manage my stack?

I’m committed this summer to finally learning docker. I’m on day 3 and the last puzzle piece is being able to access qbittorrent locally while running the container through the vpn.

  • just_another_person@lemmy.worldEnglish
    0·
    5 months ago

    If you’re learning in any kind of professional capacity, you may want to get familiar with running things on k8s. I would never deploy Compose in any kind of production environment.

    • peregus@lemmy.worldEnglish
      0·
      5 months ago

      I would never deploy Compose in any kind of production environment.

      May I ask you why?

      • just_another_person@lemmy.worldEnglish
        0·
        5 months ago

        Aside from the myriad issues it has on its own, the easiest answer is: it doesn’t scale on multiple machines and instances.

        Example: I have 10 services in a compose file, and I need each service to scale independently across multiple servers. Which is easier, more reproducible, and reliable: controlling the docker compose state across many instances, or communicating with a central management service with one command to do it all for me?

        • towerful@programming.devEnglish
          0·
          5 months ago

          Sure, but what you are describing is the problem that k8s solves.
          I’ve run plenty of production things from docker compose. Auto scaling hasn’t been a requirement, and HA was built into the application (so 2 separate VMs running the compose stack). Docker was perfect for it, and k8s would’ve been a sledgehammer.

  • synae[he/him]@lemmy.sdf.orgEnglish
    0·
    5 months ago

    Never heard of dockStarter so I’m gonna say yes

    Compose is good for getting started, and might be sufficient for a long time. Eventually I moved to k8s but I also use that for work so it was an easy move for me.