# Config.yaml - Linux/Docker all parameters **URL:** \ **Category:** Node Operators\ **Created:** [January 5, 2024, 10:52pm UTC](https://forum.storj.io/t/config-yaml-linux-docker-all-parameters/24850 "2024-01-05T22:52:03Z")\ **Posts on this page:** 1\ **Showing post:** 20
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [May 5, 2024, 12:00pm UTC](https://forum.storj.io/t/config-yaml-linux-docker-all-parameters/24850/20 "2024-05-05T12:00:04Z")
This is related only to a docker setup without redirecting logs to the file. In this case you do not need to search for a container-id and other useless things, just use `docker logs` instead. But if you did redirect to the file, then you need to setup a logrotate > [@Best method to redirect logs to independant storage in Linux](https://forum.storj.io/t/topic/8039/10): > > Hi phillipe, This is easy to do with logrotate since you can use wildcards to define your paths and files. I placed a logrotate config file in /etc/logrotate.d/ called storagenode . It is a plain text file. My logrotate config file is as follows. Don’t include comments in your config file (there is an uncommented version below). /mnt/logs-usb/storj\*/storagenode\*.log { #the wildcard (\*) characters tell logrotate to look in any subfolder that #begins with storj, and rotate any log that starts wi… In the last case you would use something like ```auto $ zcat /mnt/x/storagenode2/storagenode.log-20240501.gz | grep -E "used-space-filewalker" | tail ``` to find out when the `used-space-filewalker` have a last run (as an example). --- _[View the full topic](https://forum.storj.io/t/config-yaml-linux-docker-all-parameters/24850)._