This repository has been archived by the owner on Aug 14, 2020. It is now read-only.
app-container: try out "root-container" naming #31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on feeback from a number of folks the overloading of the
"container" has caused quite a bit of confusion. This PR tries
"root-container" on for size. Which if you think of cgroups as heirarchy like
the filesystem (which they are) makes a lot of s
This is an alternative to using a new term such as "pod", "grou
"cell". The idea is that we don't call
/
on the UNIX filesyst anythingspecial, we call it the "root-directory". So, lets see can try this on for
size here. There is a root-container and on sub-containers. Apps execute as a
direct sub-container of the root-container.
rkt/rkt#151