@grahamwhaley -- I see the same thing when doing:
docker run -it alpine sh

exit

This is a bit concerning, especially given some of the other life cycle bugs we have open.

Closing as this isn't a bug in the runtime, it's a bug in containerd afaik:

• https://github.com/01org/cc-oci-runtime/blob/master/src/oci.c#L1102

And here's the relevant snippets from a debug log showing how the runtime was called for a single container lifecycle:

$ sudo grep "called as" /var/lib/clear-containers/runtime/runtime.log|cut -d\) -f2-|tr -d :|tr -d \[|awk '{print $1,$2,$3}'
called as create
called as start
called as kill
called as delete
called as delete

So @jodh-intel , should we be changing our error to a warning, to match cc-oci-runtime better (and cause less concerning messages in the logs) ?
If so, we might want to re-open this or a new Issue.

It's very debatable. The runtime has detected that it has been called incorrectly, so that is an error. I'm easy either way though as long as we log at atleast the warning level.

OK, after irc chatter and input from @egernst I'm going to re-open this asking that we downgrade those errors to info/warnings - given that the double delete is, I believe, benign, correct @jodh-intel ?

It's benign in that the runtime catches the incorrect call from containerd and handles it, yes.
@egernst - please can you reference this bug when you raise an issue on containerd.