I set it to debug at somepoint and forgot maybe? Idk, but why the heck does the default config of the official Docker is to keep all logs, forever, in a single file woth no rotation?

Feels like 101 of log files. Anyway, this explains why my storage recipt grew slowly but unexpectedly.

  • Appoxo@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    4 hours ago

    Logration is the abc of the developer.
    Why should I need 3rd party tools to fix the work of the developer??

    • Shimitar@downonthestreet.eu
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      2
      ·
      2 hours ago

      Why is that? Really? The Dev should replace a system function? And implement over and over again the same errors when logrotate exist?

      • acockworkorange@mander.xyz
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 hour ago

        Yes, that’s exactly what we’re arguing here. The developer also should replace autotools/cmake, git, … Don’t be daft! Packaging sane defaults for logrotate is now replacing a system function?

        • sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          57 minutes ago

          Docker is supposed to run a single process Logrotate is a separate process. So unless the application handles rotating logs, the container shouldn’t handle it.