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
    5
    ·
    25 days ago

    No, then you’re just orchestrating the service level stuff, and nothing else. Docker’s tools will never compare to cluster scaling efforts where the entire horizontal layer to be scaled can be orchestrated from the instance up to containers.

    • Matt The Horwood@lemmy.horwood.cloud
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      25 days ago

      not sure I understand you, in docker swarm your containers are started on n number of works from a single compose file on a manager. you can add any number of work nodes to scale your service as needed

      • just_another_person@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        25 days ago

        N number of EXISTING nodes. Proper container orchestration platforms handle all the provisioning of instances, scaling of services, IAM…etc.

        Docker Swarm (and all Docker tools) only handle…Docker.

        Swarm is another thing I would never recommend in production.

        • Matt The Horwood@lemmy.horwood.cloud
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          25 days ago

          That’s not container orchestration, that’s infrastructure orchestration. Depending on your use case docker swarm could just the right tool for the job.

          You’ve been using Aws and they will happily let you add more nodes to your container runner of choice