Skip to content
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

If Loki becomes unreachable Containers are stuck #53

Open
frzb opened this issue Mar 6, 2022 · 0 comments
Open

If Loki becomes unreachable Containers are stuck #53

frzb opened this issue Mar 6, 2022 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@frzb
Copy link
Owner

frzb commented Mar 6, 2022

It is a know upstream issue:

The driver keeps all logs in memory and will drop log entries if Loki is not reachable and if the quantity of max_retries has been exceeded. To avoid the dropping of log entries, setting max_retries to zero allows unlimited retries; the drive will continue trying forever until Loki is again reachable. Trying forever may have undesired consequences, because the Docker daemon will wait for the Loki driver to process all logs of a container, until the container is removed. Thus, the Docker daemon might wait forever if the container is stuck.

Feeding the Docker container logs via Promtail or Fluentd into Loki and not over the Loki Docker logging driver should be sufficient as work-around.

@frzb frzb added the bug Something isn't working label Mar 6, 2022
@frzb frzb self-assigned this Mar 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant