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.
for some helpful config, the below is the logging config I have and logs have never been an issue.
You can even add
'logfile' => '/some/location/nextcloud.log',to get the logs in a different place'logtimezone' => 'UTC', 'logdateformat' => 'Y-m-d H:i:s', 'loglevel' => 2, 'log_rotate_size' => 52428800,Wow, thanks for the heads up! I use Nextcloud AIO and backups take VERY long. I need to check about those logs!
Don’t know if I’m just lucky or what, but it’s been working really well for me and takes good care of itself for the most part. I’m a little shocked seeing so many complaints in this thread because elsewhere on the Internet that’s the go-to method.
It can be fidgety, especially if you stray from the main instructions, generally I do think it’s okay, but also updates break it a bit every now and again.
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.
I would argue that logrotate was the ABC of any sysadmin in 2005, but today that should be a solved problem, whether in docker or bare metal.
This is a docker! If your docker is marketed as ready to go and all-in-one, it should have basic things like that.
If I were running this as a full system with a user base then of course I would go over everything and make sure it all makes sebse for my needs. But since my needs were just a running nc instance, it would make sense to run a simple docker with mostly default config. If your docker by default has terrible config, then you are missing the point a bit.
Containers don’t do log rotation by default and the container itself has no say in the matter. You have to configure it in your container runtime config.
Dockers images are often incoherent and just different from one a other so much that you should never give something as expected and doublecheck the basics.
Docker was never meant do deploy services, and I shows.
What? Like, yeah you are responsible to do your own checks, sure. but the fuq you said about docker?
It’s absolutely meant to deploy services, that’s its entire purpose…
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?
Is it default on every distro? If not, then it’s the responsibility of the dev.
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.
Those should also all be secure by default. What is this, Windows?
Just basic checks I prefer to ensure, not leave to distribution good faith. If all is set, good to go. Otherwise, fix and move on.
Specially with self hosted stuff that is a bit more custom than the usual.
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.
Agreed, but going container route those nice basic practices are dead.
And also, being mextcloud a php service, of can’t by definition ship with a logrotate config too, because its never packaged by your repo.
The fact (IMHO) is that the logs shouldn’t be there, in a persistent volume.
Probably, but still, if they are, just rotate them.
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.
Imho it’s because docker does away with (abstracts?) many years of sane system administration principles (like managing logfile rotations) that you are used to when you deploy bare metal on a Debian box. It’s a brave new world.
I disagree with this, container runtimes are a software like all others where logging needs to be configured. You can do so in the config of the container runtime environment.
Containers actually make this significantly easier because you only need to configure it once and it will be applied to all containers.
It’s because with docker you don’t need to do log files. Logging should be to stdout, and you let the host, orchestration framework, or whoever is running the container so logs however they want to. The container should not be writing log files in the first place, containers should be immutable except for core application logic.
Docker stores that stdout per default in a log file in var/lib/docker/containers/…
At worst it saves in the config folder/volume where persistent stuff should be.
Good point!
Or you can use Podman, which integrates nicely with Systemd and also utilizes all the regular system means to deal with log files and so on.
Does podman do the Docker networking thing where I can link containers together without exposing ports to the rest of the system? I like my docker compose setup where I only expose caddy (TLS trunking) and Jellyfin (because my TV fails connecting w/ TLS).
I think it also has that, but normally it uses an even easier concept of pods that basically wrap multiple containers into a meta container with it’s own internal networking and name space, and that does exactly what you want.
Good suggestion, although I do feel it always comes back to this “many ways to do kind of the same thing” that surrounds the Linux ecosystem. Docker, podman, … some claim it’s better, I hear others say it’s not 100% compatible all the time. My point being more fragmentation.
100 ways to configure a static ip.
Why does it need that? At least one per distro controlled by the distro-maintainers.
Everything I hear about Nextcloud scares me away from messing with it.
Yes. And then I read press announcements like this https://nextcloud.com/blog/press_releases/nextcloud-procolix-partner-netherlands/
I stopped using Nextcloud a couple of years ago after it corrupted my encrypted storage. I’m giving it a try again because of political emergency. But we sure need a long term replacement. Written in Rust or some other sane language.
I’ve considered writing my own, but it’s a ton of work. Even for my very basic use case of a file browser that offloads all edits to Collabora CODE. I had a basic system started in Go some years back, but bailed when I got a basic setup working (just file ops).
Maybe I’ll give it a shot again. I mostly use Rust now, and I’m kind of stalling on my P2P Lemmy idea anyway. I really don’t like PHP and I don’t use many of the Nextcloud features anyway. I just want Google Drive w/ LibreOffice or OnlyOffice.
My NC setup “just works” though. So I’m not super motivated to replace it.
Edit: looks like Seafile may do the trick.
Nc is great, it really is amazing that it is foss. Sure it isn’t the slickest or fastest, and it does need more maintenance than most foss services, but it is also more complex and has so many great features.
I really recommend nc, 99% of the time it just works for me. It just seems that their docker was done pretty poorly imo, but still it just works most of the time.
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.
The
price rboemproblem is that the log file is inside the container in the www folder.Edit: typo
You can move it.
Right, I should probably map the file directly to the system log folder. I’ll try that.
If you only use it for files, the only thing it’s good for imho. it’s awesome! :)
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.
Well that’s not jellyfins faults but rather watchtower…
101 of log files
is to configure it yourself
Look, defaults are a thing and if your defaults suck then you’ve made a mistake and if your default is to save a 100GB of log file in one file then something is wrong. The default in Dockers should just be not to save any log files on the persistent volumes.
Exactly. It should just write to stdout and let whatever is running it manage it.
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.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
Yes! When I read that I need a second instance for cron I was like “wtf?” I know NC are not the only ones doing that but still
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
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.
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!!
