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

SeccompProfile errnoRet field is a string but should be a uint #1769

Closed
CoreyCook8 opened this issue Jun 27, 2023 · 0 comments · Fixed by #1770
Closed

SeccompProfile errnoRet field is a string but should be a uint #1769

CoreyCook8 opened this issue Jun 27, 2023 · 0 comments · Fixed by #1770
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@CoreyCook8
Copy link
Contributor

What happened:

When trying to deploy a pod with a custom seccomp profile with a string I get
Warning Failed 45m (x8 over 47m) kubelet Error: setup seccomp: from field: load local profile: decoding seccomp profile failed: json: cannot unmarshal string into Go struct field Syscall.syscalls.errnoRet of type uint

What you expected to happen:

I expect the pod to be able to deploy with a custom errnoRet value specified.
The yaml from security-profiles-operator expects a string but requires a uint in the resulting json file.

How to reproduce it (as minimally and precisely as possible):

Create a seccomp profile with an errnoRet value specified.
Try to deploy a container with that seccomp profile in the securityContext

Anything else we need to know?:

I can't see a reason to have the errnoRet be a string value so I think it just needs to be changed to a uint.

Environment:

  • Cloud provider or hardware configuration:
  • OS (e.g: cat /etc/os-release):
  • Kernel (e.g. uname -a):
  • Others:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
1 participant