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

Document basic operations for V1, V2 and system cases #209

Open
c3d opened this issue Oct 20, 2021 · 1 comment
Open

Document basic operations for V1, V2 and system cases #209

c3d opened this issue Oct 20, 2021 · 1 comment

Comments

@c3d
Copy link

c3d commented Oct 20, 2021

In the context of kata containers, I am trying to figure out how to write code that works both for legacy and unified mode. I did not find any good example of that, and I was wondering if it is documented anywhere. If not, maybe it would be nice to update the readme and other examples with code for both cases?

Also, am I correct in understanding that the module does not presently abstract away resources in the two cases, i.e. you need to use Resources for unified and LinuxResources for legacy? Is the plan that everything will switch to Resources over time, or will that dichotomy persist?

Assuming the two interfaces will coexist in the near future, is there any function that converts from one to the other?

(I will try to answer my own questions here, but I would appreciate if someone more knowledgeable with the project can provide some guidance, notably with respect to future intent).

@c3d
Copy link
Author

c3d commented Oct 20, 2021

Possibly related is that when @sameo pulled a more recent version in kata containers PR #2332, this seems to have introduced a regression in the systemd case.

From a discussion with @fgiudici:

The cgroups creation complying with the systemd cgroups management has been dropped. See kata code. What we need seems to be to create the cgroups as explained here.

@fgiudici will provide more details once he's done analyzing the problem.

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

1 participant