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.

  • Scrubbles@poptalk.scrubbles.tech
    link
    fedilink
    English
    arrow-up
    4
    ·
    8 hours ago

    I have lost now not hours, but days debugging their terrible AIO container. Live production code stored in persistent volumes. Scattered files around the main drive in seemingly arbitrary locations. Environment variables that are consistently ignored/overrided. It’s probably my number one example of worst docker containers and what not to do when designing your container.

    • ilmagico@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 hours ago

      Yeah, their AIO setup is just bad, the more “traditional” and community supported docker compose files work well, I’ve been using them for years. They’re not perfect, but work well. Nextcloud is not bad per se, but just avoid their AIO docker.

      • grimer@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 hours ago

        I’ve only ever used the AIO and it’s the only one of my problem containers out of about 30. Would you mind pointing me to some decent community compose files? Thanks!!