Collect container exit codes across platforms about runtime-tools HOT 1 OPEN

Also tied up in “how do I collect the container exit code?” is “how do I know when the container process has exited?”. An alternative not mentioned in my brief list above would be to poll state and look for a stopped status, and then to read out the container process exit code from a (new) state field (exit-code?). That sounds like a pretty ugly user experience compared to opencontainers/runtime-spec#508, but it's probably the easiest-to-implement way to get over this particular hurdle, and I think it would be better than cutting a spec 1.0 without addressing this issue at all.

from runtime-tools.