Rant! 100GB Log file in Nextcloud.
-
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.
-
You can move it.
-
Exactly. It should just write to stdout and let whatever is running it manage it.
-
What? Like, yeah you are responsible to do your own checks, sure. but the fuq you said about docker?
-
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.
-
Right, I should probably map the file directly to the system log folder.
I'll try that. -
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.
-
Docker stores that stdout per default in a log file in var/lib/docker/containers/...
-
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.
-
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.
-
Nice! I've been having permissions conflicts between Samba (installed system-wide) and Jellyfin (docker), so it's probably as good a time as any to try out podman since I need to mess with things anyway.
-
Or you can forward to your system logger, like syslog or systemd.
But then projects like NextCloud do it all wrong by using a file. Just log to stdout and I'll manage the rest.
-
You can configure the default or override per service. This isn't something containers should be doing.
-
There's basically three types of networking config:
- direct with the kernel - don't do this
- some distro-specific abstraction - e.g. /etc/network/interfaces for Debian
- networking manager - wicked, network manager, etc
I do the last one because it's distro-agnostic. I use Network Manager and it works fine.
-
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.
-
I notice that you replied to me once again in connection to me mentioning static IP and linux.
Can I summon you this way? ^^ -
Apparently. I was wondering if you were the same person.
I'm just a happy Linux user trying to help when other people run into problems.
-
You are right and as others have pointed out correctly it’s Nextcloud not handling logging correctly in a containerized environment. I was ranting more about my dislike of containers in general, even though I use the technology (correctly) myself. It’s because I am already old on the scale of technology timelines.
-
Totally okay. Hope it helps somone trying to search for solutions on th web
