Comment on Rant! 100GB Log file in Nextcloud.

JASN_DE@feddit.org ⁨1⁩ ⁨month⁩ ago

• scrubbles@poptalk.scrubbles.tech ⁨1⁩ ⁨month⁩ ago

  Persistent storage should never be used for logging in docker. Nextcloud is one of the worst offenders of breaking docker conventions I’ve found, this is just one of the many ways they prove they don’t understand docker.

  Logs should simply be logged to stdout, which will be read by docker or by a logging framework. There should never be “log files” for a container, as it should be immutable, with persistent volumes only being used for configuration or application state.

  source

  • exu@feditown.com ⁨1⁩ ⁨month⁩ ago

    The AIO container is so terrible, like, that’s not how you’re supposed to use Docker.
    It’s unclear whether OP was using that or saner community containers, might just be the AIO one.

    source

    • merthyr1831@lemmy.ml ⁨1⁩ ⁨month⁩ ago

      It’s too late for me now coz I didnt do my research and ive already migrated over, but good god ever loving fuck was the AIO container the hardest of all my services to set up.

      Firstly, it throws a fit if you don’t set up the filesystem specifically for php and the postgres db as if it were bare metal. Idk how or why every other container I use can deal with UID 568 but Nextcloud demands www-data and netdata users.

      When that’s done, you realise it won’t run background tasks because it expects cron to be set up. You have to set a cronjob that enters the container to run the cron, all to avoid the “recommended” approach of using a second nextcloud instance just to run background tasks.

      And finally, and maybe this is just a fault of TrueNAS’ setup wizard but, I still had to enter the container shell to set up a bunch of basic settings like phone region. come on.

      Straight up worse than installing it bare metal

      source