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.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    6 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.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      6 months ago

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

      May I ask you why?

      • just_another_person@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 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?