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

Initial logs of an application container are lost #17

Open
pajachiet opened this issue May 30, 2018 · 0 comments
Open

Initial logs of an application container are lost #17

pajachiet opened this issue May 30, 2018 · 0 comments

Comments

@pajachiet
Copy link

When an application container starts, its logs are not streamed to logmatic until the next tick of logmatic-docker.

This behavior loses up to 30s of logs. (30s = default logmatic-docker interval between ticks)
It may not be a problem for long running containers, but this loses most of the logs for short jobs.

One solution could be to push all available logs on running containers, as proposed in this issue. A way to do that could be to use containers.attach rather than container.logs, as tried in this commit.

Another solution could be to use the since parameter, as tried in this commit.

A hack we currently do to get all the logs is to sleep 30 seconds in the container, before starting the main command…

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant