-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
why mount logs on volume? #96
Comments
Hey @0x13A, that way you can access the logs from the host. If your container crashes on boot or you just want to use your host's tools it's quite useful. If you're running NoDock in production, it makes it easier to use log monitoring software. Let me know if this answers your question 😄 |
You can still check logs with I guess is against the idea of docker compose to have logs mounted on the host machine |
Fair point. ELK sounds like the way to go for production but as far as development environments go I think we still need direct access to the logs for simplicity's sake. I think this can be separated into 2 issues:
@0x13A Any more thoughts on this? |
Makes sense! |
Is there a specific reason why you want to mount logs on volume? https://github.com/Osedea/nodock/blob/f851f5e/docker-compose.yml#L59
The text was updated successfully, but these errors were encountered: