You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After running this image for a few weeks, the container log file has grown to almost 200 GB. I needed to reclaim space so I stopped the container, truncated the log file, limited the log file size, and restarted the container. Not sure if this is normal/expected or if I have something misconfigured.
I added the following to docker compose if anyone else sees a similiar issue.
Ah, I did have debug enabled. Forgot that I had even enabled it when first setting up. Forgot to disable after I got things running successfully. That is still a lot. Might want to look at using files for logging with file rotation down the road. Maybe a file a day and keep a week's worth of logs or something along those lines. I like the way the arr's do it with separate files for info versus debug versus trace as well.
After running this image for a few weeks, the container log file has grown to almost 200 GB. I needed to reclaim space so I stopped the container, truncated the log file, limited the log file size, and restarted the container. Not sure if this is normal/expected or if I have something misconfigured.
I added the following to docker compose if anyone else sees a similiar issue.
Everything seems to be running normally
The text was updated successfully, but these errors were encountered: