Skip to content
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

Write a "Getting Started" guide #32

Closed
samuelkarp opened this issue Dec 2, 2018 · 2 comments
Closed

Write a "Getting Started" guide #32

samuelkarp opened this issue Dec 2, 2018 · 2 comments
Assignees
Labels
documentation Issue related to documentation
Milestone

Comments

@samuelkarp
Copy link
Contributor

We need a guide to help users and contributors get started with firecracker-containerd. #16 is part of the process, but we also need to cover installation and configuration of all required components.

@samuelkarp samuelkarp added the documentation Issue related to documentation label Dec 2, 2018
@samuelkarp samuelkarp self-assigned this Dec 2, 2018
@samuelkarp samuelkarp added this to the hello world milestone Dec 2, 2018
@IRCody
Copy link
Contributor

IRCody commented Dec 3, 2018

Some things that I remember have come up that are not documented atm:

  • Should use relative path as the socket_path inside. If this isn't done, because the socket isn't cleaned up cleanly every time. This results in behavior where you have roughly 50/50 success/error of starting firecracker. Relative path creates the socket inside the bundle dir which is unique per container.
  • The cri plugin must currently be disabled for unknown reasons. I created Figure out why cri plugin must be disabled #35 to track this. This can be done by adding disabled_plugins = ["cri"] to the top of the /etc/containerd/config.toml file and restarting containerd.

@samuelkarp
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Issue related to documentation
Projects
None yet
Development

No branches or pull requests

2 participants