Skip to content

[pull] master from moby:master#917

Merged
pull[bot] merged 5 commits intonext-stack:masterfrom
moby:master
May 8, 2020
Merged

[pull] master from moby:master#917
pull[bot] merged 5 commits intonext-stack:masterfrom
moby:master

Conversation

@pull
Copy link
Copy Markdown

@pull pull bot commented May 8, 2020

See Commits and Changes for more details.


Created by pull[bot]. Want to support this open source service? Please star it : )

tonistiigi and others added 5 commits April 24, 2020 11:22
This version avoids doing name lookups on creating tarball that
should be avoided in to not hit loading glibc shared libraries.

Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
(cherry picked from commit aa6a989)
Signed-off-by: Tibor Vass <tibor@docker.com>
This blurb exists because we reused the same commit from an old patch,
and thus got the commit message with it. However the message is
confusing in this context.
It was suggested in review that we should remove the confusing message.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
This prevents getting into a situation where a container log cannot make
progress because we tried to rotate a file, got an error, and now the
file is closed. The next time we try to write a log entry it will try
and rotate again but error that the file is already closed.

I wonder if there is more we can do to beef up this rotation logic.
Found this issue while investigating missing logs with errors in the
docker daemon logs like:

```
Failed to log message for json-file: error closing file: close <file>:
file already closed
```

I'm not sure why the original rotation failed since the data was no
longer available.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
logfile: Check if log is closed on close error during rotate
@pull pull bot added the ⤵️ pull label May 8, 2020
@pull pull bot merged commit cdf49f3 into next-stack:master May 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants