For the vast majority of docker images, the documentation only mention a super long and hard to understand “docker run” one liner.

Why nobody is placing an example docker-compose.yml in their documentation? It’s so tidy and easy to understand, also much easier to run in the future, just set and forget.

If every image had an yml to just copy, I could get it running in a few seconds, instead I have to decode the line to become an yml

I want to know if it’s just me that I’m out of touch and should use “docker run” or it’s just that an “one liner” looks much tidier in the docs. Like to say “hey just copy and paste this line to run the container. You don’t understand what it does? Who cares”

The worst are the ones that are piping directly from curl to “sudo bash”…

  • casrou@feddit.dk
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    That is one docker compose up -d for each file you copied over, right… Or are you doing something even smarter?

    • Morethanevil@lmy.mymte.de
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      I have one docker-compose.yml for each service. You can use docker compose -f /path/to/docker-compose.yml up -d in scripts

      I would never use “one big” file for all. You only get various problems imo

      • SheeEttin@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        You use a separate file for each service? Why? I use one file for each stack, and if anything, breaking them out would give me issues.

        • Morethanevil@lmy.mymte.de
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          I meant stack 😸

          My structure is like

          /docker/immich/docker-compose /docker/synapse/docker…

          But I read that some people make one big file for everything