-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Respect NanoCpus in Compat Create #9607
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mheon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
LGTM |
test/apiv2/20-containers.at
Outdated
@@ -263,3 +263,12 @@ t GET containers/json 200 \ | |||
.[0].Ports[0].Type="tcp" | |||
|
|||
podman stop bar | |||
|
|||
# Test CPU limit (NanoCPUs) | |||
t POST containers/create '"Image":"'$IMAGE'","HostConfig":{"NanpCpus":500000}' 201 \ |
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.
typo in NanpCpus
?
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.
Good catch... I was trying to figure out why this wasn't being set.
The NanoCpus field in HostConfig was not wired up. It conflicts with CPU period and quota (it hard-codes period to a specific value and then sets the user-specified value as Quota). Fixes containers#9523 Signed-off-by: Matthew Heon <[email protected]>
APIv2 test is green, this looks like CI will pass. @containers/podman-maintainers PTAL |
/hold |
/lgtm |
/hold cancel |
The NanoCpus field in HostConfig was not wired up. It conflicts with CPU period and quota (it hard-codes period to a specific value and then sets the user-specified value as Quota).
Fixes #9523