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

Fix stderr comment in containerd-shim serve command #995

Merged
merged 1 commit into from Apr 8, 2021

Conversation

dcantah
Copy link
Contributor

@dcantah dcantah commented Apr 8, 2021

In a comment in the serve command for the containerd-shim it says that to signify that we're
successfully serving the ttrpc endpoint we should close stderr, but we actually seem to close stdout
to signify this. The write end of the pipe is hooked up to stdout on the "serve" command invocation
of the shim and we simply forward stderr to the read side until close. Stderr for the serve
invocation is hooked up to the panic.log file

Signed-off-by: Daniel Canter dcanter@microsoft.com

In a comment in the serve command for the containerd-shim it says that to signify that we're
successfully serving the ttrpc endpoint we should close stderr, but we actually close stdout
to signify this. The write end of the pipe is hooked up to stdout on the "serve" command invocation
of the shim and we simply forward stderr to the read side until close. Stderr for the serve
invocation is hooked up to the panic.log file in case the shim panics.

Signed-off-by: Daniel Canter <dcanter@microsoft.com>
@dcantah dcantah requested a review from a team as a code owner April 8, 2021 10:53
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

Successfully merging this pull request may close these issues.

None yet

2 participants