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

Use Kata containers for better isolation #334

Open
ishitatsuyuki opened this issue May 7, 2018 · 4 comments
Open

Use Kata containers for better isolation #334

ishitatsuyuki opened this issue May 7, 2018 · 4 comments

Comments

@ishitatsuyuki
Copy link
Contributor

Kata containers are a way to run Docker container in a VM-like fashion, which allows us to grant almost any permission with much less risk of getting exploited of a kernel bug.

This has a few downsides:

  • KVM is required, which means it won't run on EC2 or similar VM providers
  • cgroups are not supported yet, and maybe the memory management is harder due to the virtualizing nature
@sr229
Copy link

sr229 commented Jan 25, 2019

I think we circumvent that by using Kubernetes for Janitor. This is how exactly how Gitpod is doing it.

@jankeromnes Opnions on this.

@ishitatsuyuki
Copy link
Contributor Author

@sr229 All Kubernetes has is a slightly more strict seccomp profile, so it doesn't add security nor loosen the debugging restriction. What are you proposing?

@sr229
Copy link

sr229 commented Jan 26, 2019

@ishitatsuyuki in Kubernetes, Kata Containers aren't subject to its Docker limitations, so using a Kubernetes runtime is more plausible than just using Docker all-in-all due to the networking limitations and a whole lot more documented.

@ishitatsuyuki
Copy link
Contributor Author

I don't think Kubernetes is worth its complexity in this case. Not having a networked storage is the main reason, and secondly we probably don't want a big refactoring on Janitor codebase itself because it's too much work.

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

No branches or pull requests

2 participants