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

LOCALHOSTPROFILE empty - Unable to install any SeccompProfile #2498

Open
emzxcv opened this issue Oct 10, 2024 · 0 comments
Open

LOCALHOSTPROFILE empty - Unable to install any SeccompProfile #2498

emzxcv opened this issue Oct 10, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@emzxcv
Copy link

emzxcv commented Oct 10, 2024

What happened:

I installed SOP via Helm.
helm install security-profiles-operator --namespace security-profiles-operator https://github.com/kubernetes-sigs/security-profiles-operator/releases/download/v0.8.4/security-profiles-operator-0.8.4.tgz

image

What you expected to happen:

LOCALHOSTPROFILE should be populated so it can be referenced by pods as the LocalhostProfile field.

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

Just install SOP 0.8.4, create a seccompprofile resource in the SAME namespace. It should create but never reach any status of 'Installed' and LOCALHOSTPROFILE is empty.

Anything else we need to know?:

I have tried creating in default namespace and the security-profiles-operator where i installed SOP. Both do not work.

Two of the 3 pods seem to have this log:

image

Environment:

  • Cloud provider or hardware configuration: GKE
  • OS (e.g: cat /etc/os-release):
  • Kernel (e.g. uname -a):
  • Others:
@emzxcv emzxcv added the kind/bug Categorizes issue or PR as related to a bug. label Oct 10, 2024
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
Development

No branches or pull requests

1 participant