Some questions about error handling on runc, crun or other runtime

[payall4u]

Runc and crun will go different error message when delete a non-existent container, such as:
runc got container <container-id> does not exist
crun got error opening file 'container-status': No such file or directory\n: unknown"
But containerd and shim will identify these errors by error message. Some runc error can be recognized and handle correctly, but crun can't.
We already have a lot runtime tools, and containerd-shim-v2 can be used with any runtime tools. Should error messages of them be standardized?

[giuseppe]

maybe we could at least agree on a few exit codes so that container engines don't have to parse the error string.

[cyphar]

I agree that standardising some basic exit codes would be a good idea.

[utam0k]

@giuseppe @cyphar @AkihiroSuda
What is the status of this issue? I have interested in this. This is a good idea!

[utam0k]

How about simply adding 255 to the error code if there is an error inside OCI Runtime? It would be easier for the client to handle.