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
runtime: add SingleContainer when obtaining OCI Spec #8974
runtime: add SingleContainer when obtaining OCI Spec #8974
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm, thanks!
/test |
// represents the pause container. In Docker, this is the container. | ||
// On Linux, we derive the group path from this container. | ||
// Get the container associated with the PodSandbox annotation. | ||
// In Kubernetes, this represents the pause container. In Docker, this is the container. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that "In Docker" is not appropriate today. Should we make it more generic?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I changed it to "CRI-compatible runtime like Containerd"
When creating a cgroup, add a SingleContainer when obtaining the OCI Spec to apply to ctr, podman, etc. Fixes: kata-containers#5240 Signed-off-by: yaoyinnan <35447132+yaoyinnan@users.noreply.github.com>
701d4c0
to
9aa1ed8
Compare
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thx @yaoyinnan LGTM!
When creating a cgroup, add a SingleContainer when obtaining the OCI Spec to apply to ctr, podman, etc.
Fixes: #5240