Suggestion: Move containerd.IO code as independent containerd repo

[kunalkushwaha]

By containerd.IO I mean io.go, io_unix.go & io_windows.go.

Implementation of IO interface for containerd is completely independent of containerd code, So it can be easily move to independent repo and shall be helpful in reusing code with including whole containerd repo.

[crosbymichael]

I'm not sure the code is meaningful enough outside of the context of containerd to warrant a separate repo. It would have to be used by multiple projects before we did something like this I think.

Could you explain more why you think this code should be separate?

[kunalkushwaha]

Could you explain more why you think this code should be separate?

I am writing one testing tool which can runs same test cases on multiple container runtime. Am thinking to resue this code for other runtimes like cri-o.

I think, I concluded too early for reusing this code. Will implement this first and if required will open this issue.

Sorry for false alarm.
Closing this issue as of now.

[AkihiroSuda]

see #1782 @kunalkushwaha