[Bug Report] Log file consumes all remaining HDD space associated with Docker system about docker-palworld-dedicated-server HOT 3 CLOSED

1. Are you sure that the logs from this container are the issue? Can you give an example of the actual logs you're getting? Once Palworld has started it should not be logging that much, unless you have the cron jobs set to run very often.
2. The json-file logging driver in Docker has a lot of overhead (produces very large files for the amount of logging it stores). If you don't need the extra parsing functionality it gives you, I recommend switching to either the local logging driver, or if you have some kind of central logging manager on your system, switching to a logging driver that takes better advantage of that, such as syslog or journald.

from docker-palworld-dedicated-server.

You could add Logrotation 15MB times 3 in Docker to solve this. Pretty sure the image itself isnt that verboose, but if you let it run long enough with debug-logs it can grow quite big i guess.

from docker-palworld-dedicated-server.

Im closing this issue as resolved, feel free to reach out again if you need help.

If you like this project, please consider giving this repo and the Docker-Hub-Repo a Star.

from docker-palworld-dedicated-server.