And in today’s news: heroic container fills 1Tb drive with logs to crash server. “Fuck Docker” says admin

  • 1
    Generating enough logs to fill a TB is quite an achievement indeed.

    Maybe, you need to set some quotas...
  • 0
    Did you leave it on loglevel=all?
  • 0
    Naw some other container took a shit and this one started spamming lots of errors, logs didn’t go where they were sposed to for logrotate to clean up, so...probably going back to bare metal on monday, had enough of all this shit
  • 0
    Happened to me on a root server once, without a separated /var partition by OpenLDAP delivered with debug logging (e.g. for missing indices) paired with a buggy cronjob doing a lot of queries.

    Will never make this mistake again.
  • 0
    *gitlab memories intensifies*

    Had the same problem with gitlab + docker. 25 GB a day log files. Wtf?!
Add Comment