You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this container is abandonware or not, but I just discovered and implemented it, and it seems perfect for me with one small exception.
I have all of my containers set to place all of their logs in a central location on the host (/mnt/e/logs) and then a subdir per container.
In my case, it would be cleaner and more efficient to just mount the top-level dir as the volume mount, and then use an env var to ignore specific dirs (some containers have built in rotate mechanisms that I don't need this container to rotate for them).
Currently, I have to mount something like 20 containers, and also add them each on the single env var line, like this:
LOGS_DIRECTORIES: '/mnt/e/Docker/Logs/authelia /mnt/e/Docker/Logs/mysql /mnt/e/Docker/Logs/something /mnt/e/Docker/Logs/somethingelse' (etc., for another 15 or so more)
Hi
I'm not sure if this container is abandonware or not, but I just discovered and implemented it, and it seems perfect for me with one small exception.
I have all of my containers set to place all of their logs in a central location on the host (
/mnt/e/logs
) and then a subdir per container.In my case, it would be cleaner and more efficient to just mount the top-level dir as the volume mount, and then use an env var to ignore specific dirs (some containers have built in rotate mechanisms that I don't need this container to rotate for them).
Currently, I have to mount something like 20 containers, and also add them each on the single env var line, like this:
Having an env var something like:
Would be much nicer, because then I'd just mount the top-level dir, let logrotate recurse through all subdirs, and ignore just like, 3 directories. :)
The text was updated successfully, but these errors were encountered: