Skip to content
This repository has been archived by the owner on Jul 28, 2021. It is now read-only.

GCS not always returning exit code for a process #153

Closed
jterry75 opened this issue Oct 31, 2017 · 1 comment
Closed

GCS not always returning exit code for a process #153

jterry75 opened this issue Oct 31, 2017 · 1 comment
Assignees
@jterry75

Comments

@jterry75
Copy link
Contributor

@jhowardmsft - Logging for ya.

Running a command like:
docker run --rm ubuntu bash exit 123

Will return in an exit code from the HCS of 0.
@jterry75 jterry75 self-assigned this Oct 31, 2017
@lowenna
Copy link
Contributor

lowenna commented Oct 31, 2017

Ha, yeah I forgot to open. Thanks!

jterry75 added a commit that referenced this issue Nov 7, 2017
@jterry75
Fixing issues with process exit
623b292 
Resolves: #153 - Init process exit codes are not always returning because the container exited notification returns before the WaitProcess call comes in causing the HCS to teardown the container.
Resolves: #126 - WaitProcess should honor the timeout associated with the call and return the proper error response on timeout.
@jterry75 jterry75 mentioned this issue Nov 7, 2017
Merged
jterry75 added a commit that referenced this issue Nov 8, 2017
@jterry75
Fixing issues with process exit
974b40e 
Resolves: #153 - Init process exit codes are not always returning because the container exited notification returns before the WaitProcess call comes in causing the HCS to teardown the container.
Resolves: #126 - WaitProcess should honor the timeout associated with the call and return the proper error response on timeout.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jterry75 jterry75

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jterry75 @lowenna