New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate a potential role of containerd in VIC Engine #3629

Open
vburenin opened this Issue Jan 17, 2017 · 0 comments

Comments

Projects
None yet
3 participants
@vburenin
Contributor

vburenin commented Jan 17, 2017

As a developer, I need to understand a role of containerd in VIC engine life in order to figure out what our next steps should be.

Work items

  • Investigate containerd and make it working locally if it is possible.
  • Figure out how docker is using containerd, where it sits and how calls are made.
  • Start contributing into containerd project as simple bug fixes if possible.
  • Get in touch and meet with containerd dev team if possible.
  • Document findings about containerd.
  • investigate infrakit
  • identify misalignment with port-layer
  • identify bias in the portlayer as well as in the containerd/infrakit/driver model if present

@hickeng hickeng referenced this issue Jan 18, 2017

Open

Portlayer: client #3640

0 of 3 tasks complete

@mdubya66 mdubya66 removed the Spike label Feb 13, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment