-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Clarify meaning of --cgroup-parent #141
Comments
I think that for relative case it should be
But for abs, it should be
|
@mrunalp but it's impossible, I can't leave mount namespace of container to create
treat my
as |
So, I disabled my systemd noise, now path with parents:
|
So, we basically don't understand for what we need absolute paths. You can't create cgroups in parent namespace anyway and if you want to use existing cgroup from host you can use only your own cgroup, so you always can use relative path. |
@LK4D4 absolute paths are required for providing QoS tiers. These cgroups can be created from within the root namespace. Unless we provide subcontainer capabilities, I don't see a need for |
@vishh Could you provide example how it should look? Because now they're(abs and rel) identical. |
If the path is relative, then the cgroups are expected to be created under the cgroup of the calling process. Ex: cgroups created under |
Should this be closed? The |
@fabiokung it's still exitst in libcontainer but I still didn't get it :D But I'll delay to personal meeting with Vishnu. |
Now, as I see abs and rel paths for
--cgroup-parent
creates identical cgroup hierarchy.it looks like this for both cases. Seems like for
--cgroup-parent
it should be likeright?
ping @vishh @mrunalp
The text was updated successfully, but these errors were encountered: