59
Rant! 100GB Log file in Nextcloud. (lemmy.world)
submitted 2 years ago by to c/selfhosted@lemmy.world
76 comments fedilink hide all child comments
 

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 are viewing a single comment's thread
view the rest of the comments
[–] 16 points 2 years ago (3 children)

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.

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 50 points 2 years ago (3 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 5 points 2 years ago* (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    100 ways to configure a static ip.
    Why does it need that? At least one per distro controlled by the distro-maintainers.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    I notice that you replied to me once again in connection to me mentioning static IP and linux.
    Can I summon you this way? ^^

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    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).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago* (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •