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.

  • Shimitar@downonthestreet.euEnglish
    1·
    14 days ago

    Are you crazy? I understand that we are used to dumbed down stuff, but come on…

    Rotating logs is in the ABC of any sysadmin, even before backups.

    First, secure your ssh logins, then secure your logs, then your fail2ban then your backups…

    To me, that’s in the basic stuff you must always ensure.

    • Appoxo@lemmy.dbzer0.comEnglish
      0·
      14 days ago

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

      • Shimitar@downonthestreet.euEnglish
        1·
        13 days 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.xyzEnglish
          0·
          13 days 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.worksEnglish
            1·
            13 days 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.