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.
You should always setup logrotate. Yes the good old Linux logrotate…
I don’t disagree that logrotate is a sensible answer here, but making that the responsibility of the user is silly.
Are you crazy? I understand that we are used to dumbed down stuff, but come on…
Rotating logs is in the ABC of any sysadmin, even before backups.
First, secure your ssh logins, then secure your logs, then your fail2ban then your backups…
To me, that’s in the basic stuff you must always ensure.
Logration is the abc of the developer.
Why should I need 3rd party tools to fix the work of the developer??Why is that? Really? The Dev should replace a system function? And implement over and over again the same errors when logrotate exist?
Yes, that’s exactly what we’re arguing here. The developer also should replace autotools/cmake, git, … Don’t be daft! Packaging sane defaults for logrotate is now replacing a system function?
Docker is supposed to run a single process Logrotate is a separate process. So unless the application handles rotating logs, the container shouldn’t handle it.
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.
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.
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.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.
Be too, and I went back to the standalone community container
Wait there’s a community one?
I meant this one: https://hub.docker.com/_/nextcloud
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! :)
