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

Support DeviceCgroupRules to actually get added. #10895

Merged
merged 1 commit into from
Jul 24, 2021

Conversation

rhatdan
Copy link
Member

@rhatdan rhatdan commented Jul 9, 2021

Fixes: #10302

Signed-off-by: Daniel J Walsh dwalsh@redhat.com

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 9, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhatdan

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 9, 2021
@rhatdan rhatdan force-pushed the devices branch 4 times, most recently from a095484 to d8f5f51 Compare July 11, 2021 17:46
@TomSweeneyRedHat
Copy link
Member

Lots of Red test unhappiness.
The code LGTM

@@ -239,6 +239,9 @@ type ContainerStorageConfig struct {
// Devices are devices that will be added to the container.
// Optional.
Devices []spec.LinuxDevice `json:"devices,omitempty"`
// DeviceCGroupRule are device cgroup rules that allow containers
// to use additional types of devices.
DeviceCGroupRule []string `json:"device_cgroup_rule,omitempty"`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we do the parsing on the frontend, so we can pass a struct here (including the type, path, and access permissions)?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would require all users of the API to do the processing. I believe this is something that Docker supports as well.
WDYT @jwhonce @baude

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally speaking, we try to parse in the frontend to the greatest extent possible, so the server does not have to do much validation of the contents of specgen.

Fixes: containers#10302

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
@TomSweeneyRedHat
Copy link
Member

LGTM
But I'd like @mheon to eyeball and merge if his concern has been answered.

@cdoern
Copy link
Contributor

cdoern commented Jul 23, 2021

LGTM, just a general note: wondering if in the future we should look to combine all []spec. elements into a singular entity since one spec entity should contain all of the things we are referencing?

@rhatdan rhatdan added the lgtm Indicates that a PR is ready to be merged. label Jul 24, 2021
@openshift-merge-robot openshift-merge-robot merged commit ec5c7c1 into containers:main Jul 24, 2021
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

podman run --device-cgroup-rule option is not honored
5 participants