@Random-Liu
We may want to do something at some point to alleviate the need to port changes from containerd all the time. Maybe some kind of better API or library for shims to use? Do other shims depend on containerd in this way?

We may want to do something at some point to alleviate the need to port changes from containerd all the time. Maybe some kind of better API or library for shims to use? Do other shims depend on containerd in this way?

I think the containerd-shim code is expected to be eventually very stable, the porting change cases should be less and less. So I'm currently not too worry about that.

And it is good that we can get the same bug fix from containerd-shim, because it is more battle tested. :)

Merge based on #14 (comment)

We may want to do something at some point to alleviate the need to port changes from containerd all the time. Maybe some kind of better API or library for shims to use? Do other shims depend on containerd in this way?

I think the containerd-shim code is expected to be eventually very stable, the porting change cases should be less and less. So I'm currently not too worry about that.

And it is good that we can get the same bug fix from containerd-shim, because it is more battle tested. :)

Yah, I'm just thinking I'd rather we were able to vendor that code as a library rather than merge it :)