Submitted 5 weeks ago by MTK@lemmy.world to selfhosted@lemmy.world
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.
Everything I hear about Nextcloud scares me away from messing with it.
If you only use it for files, the only thing it’s good for imho. it’s awesome! :)
Just use the official Docker AIO and it is very, very little trouble. It’s by far the easiest way to use Nextcloud and the related services like Collabora and Talk.
I’m considering switching to Seafile. I just need documents to sync and Collabora integration, and it seems to do both without dealing with PHP nonsense.
Feels like blaming others for not paying attention.
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.
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.
101 of log files
is to configure it yourself
Reminds me of when my Jellyfin container kept growing its log because of something watchtower related. Think it ended up at 100GB before I noticed. Not even debug, just failed updates I think. It’s been a couple of months.
Shimitar@downonthestreet.eu 5 weeks ago
You should always setup logrotate. Yes the good old Linux logrotate…
catloaf@lemm.ee 5 weeks ago
We should each not have to configure log rotation for every individual service. That would require identify what and how it logs data in the first place, then implementing a logrotate config. Services should include a reasonable default in logrotate.d as part of their install package.
sugar_in_your_tea@sh.itjust.works 5 weeks ago
Docker services should let docker handle it, and the user could then manage it through Docker or forward to some other logging service (syslog, systemd, etc). Processes in containers shouldn’t touch rotation or anything, just log levels and maybe which types of logs go to stdout vs stderr.
RubberElectrons@lemmy.world 5 weeks ago
Ideally yes, but I’ve had to do this regularly for many services developed both in-house and out of house.
Solve problems, and maybe share your work if you like, I think we all appreciate it.
non_burglar@lemmy.world 5 weeks ago
I don’t disagree that logrotate is a sensible answer here, but making that the responsibility of the user is silly.