-
Notifications
You must be signed in to change notification settings - Fork 70
Support containerd 1.0 #292
Comments
@devimc @jcvenegas @sameo what about support for 2.1 ? |
I tested
I replaced runc by cc-runtime ( I am looking to register an new runtime to the contianerd daemon)
|
I just seen that @sameo gist describe how to add a runtime |
Running contianerd integration test , I see the runtime hanging randomly at kill command, also cc-shim and qemu are still running.
|
Update: containerd integration tests:
|
virtcontainers : fix shared dir resource remaining
Docker is planning to switch their stack from the current 0.2.4
containerd to a completely new
containerd` 1.0 implementation.There are many architectural changes with this new
containerd
implementations, and we may be impacted by mostly 2 of them:A new GRPC interface for the shim.
containerd
no longer calls directly into containerd-shim but talks to a GRPC socket instead. By defaultcontainerd
1.0 ships with a canonical implementation (containerd-shim
) for this GRPC interface but we should eventually implement it as part of our own shim implementation and get rid of one layer from our Docker based container stack.A strong bound to
runc
.containerd
heavily relies on the latest and greatestrunc
CLI which is not specified anywhere. It takes severalrunc
specific assumptions as well. We will have to implement most of the missingrunc
options on order to safely work withcontainerd
1.0.I put together a quick gist to run CC 3.0 with test the latest
containerd
code: https://gist.github.com/sameo/fa32cfe4f7a74d9eea74982bb1f0100d.The text was updated successfully, but these errors were encountered: