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
logging: fix data race in logging binary that loses container output
The logging binary had a goroutine that closed internal pipe writers
immediately upon container exit (via gRPC notification). This raced
with copyStream, which was still draining data from the external pipe.
When the gRPC notification arrived before copyStream finished, the
pipe writer was closed mid-copy, causing remaining data to be lost.
Fix by making copyStream responsible for closing the pipe writers
after all data has been copied. The container-exit goroutine (and its
getContainerWait infrastructure) is removed — pipe closure now happens
naturally when the parent process exits or the shim closes the pipe.
Fixes#4782
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
0 commit comments