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

device_ownership_from_security_context = true Is this supported ? #397

Open
socceranoo opened this issue Aug 28, 2024 · 2 comments
Open

Comments

@socceranoo
Copy link

socceranoo commented Aug 28, 2024

Expected Behavior

CRIO./containerd implements device_ownership_from_security_context = true
where the device mounts follows the security context declared in the POD spec

Actual Behavior

Cri-dockerd / docker doesnt honor the pwermissions of devices to that of the user

Steps to Reproduce the Problem

Specifications

  • Version: 0.3.0
  • Platform: RockyLinux
  • Subsystem: docker-26
@afbjorklund
Copy link
Contributor

afbjorklund commented Aug 28, 2024

It seems like this kubernetes 1.22 feature was never ported over to the docker runtime:

As mentioned in the release blog (that only talks about cri-o and containerd, not docker):

@afbjorklund
Copy link
Contributor

afbjorklund commented Aug 28, 2024

As far as I can tell, it is missing from the docker API parameters:

// DeviceMapping represents the device mapping between the host and the container.
type DeviceMapping struct {
        PathOnHost        string
        PathInContainer   string
        CgroupPermissions string
}

So there doesn't seem to be a way to change the Linux.Device

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

2 participants