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.

  • non_burglar@lemmy.worldEnglish
    0·
    4 days ago

    I don’t disagree that logrotate is a sensible answer here, but making that the responsibility of the user is silly.

    • Shimitar@downonthestreet.euEnglish
      0·
      3 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.

      • MTK@lemmy.worldOPEnglish
        0·
        3 days ago

        This is a docker! If your docker is marketed as ready to go and all-in-one, it should have basic things like that.

        If I were running this as a full system with a user base then of course I would go over everything and make sure it all makes sebse for my needs. But since my needs were just a running nc instance, it would make sense to run a simple docker with mostly default config. If your docker by default has terrible config, then you are missing the point a bit.

        • truthfultemporarily@feddit.orgEnglish
          1·
          3 days ago

          Containers don’t do log rotation by default and the container itself has no say in the matter. You have to configure it in your container runtime config.