Deprecate dockershim in vendor and change to use new containerd based architecture about frakti HOT 10 CLOSED

@t3hmrman Exactly, we are actively working on containerd + Kata with folks from Google and Hyper. There will be no docker & dockershim needed in the frakti v2 project.

from frakti.

The containerd plugin has been temporarily implemented on this dev branch: https://github.com/hyperhq/kata-runtime/tree/shimv2

from frakti.

hey @resouer Thanks so much for the pointer, I haven't actually seen the RuntimeClass proposal at all.

That makes total sense, frakti becoming a well-integrated containerd plugin sounds great -- I'm a huge fan of containerd (+ cri-containerd, the intergration was pretty smooth for them).

Thanks for taking the time to explain!

from frakti.

Just wanted to note that Frakti v2 looks really exciting to me -- one of my biggest wants was to use frakti as it exists now with cri-containerd (which is what I run now). It looks like frakti v2 will "upgrade" (IMO, some may not consider docker -> containerd an upgrade possibly) both the runV side and the docker side.

Actually came in to make a ticket requesting clarification on how to use containerd instead of docker but looks like I won't need to :)

from frakti.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from frakti.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

from frakti.

Hey @resouer to make sure I clearly understand, which of these are right:

• Frakti v2 will be a containerd plugin (similar to how cri-containerd is now a in-tree plugin)
• Frakti v2 will be rolled into the kata-containers

Those two facts seem at odds, because containerd already has an untrusted workload runtime option (on which you could set kata-runtime to run your untrusted workloads) -- Also, it doesn't really make sense for Frakti to merge into kata-runtime because Frakti is supposed to be able to handle both untrusted and trusted runtimes.

Is there somewhere I could read a bit more about how the project is moving? I'm helicoptering by and not watching closely but if there's some mailing list or forum I could read I'll go do that.

from frakti.

Hi @t3hmrman, not sure if you have read the RuntimeClass proposal? See: https://github.com/kubernetes/community/blob/master/keps/sig-node/0014-runtime-class.md

It's exactly where we are going. The trusted/untrusted annotations will be deprecated, and frakti v2 will only include several containerd focus plugins to handle runtimes, networking, and storage. And of course, a doc about how to set these pieces up to serve as a production ready runtime for Kubernetes.

from frakti.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

from frakti.

@fejta-bot: Closing this issue.

from frakti.