Replies: 9 comments
-
I confirmed that bottlerocket uses containerd, as |
Beta Was this translation helpful? Give feedback.
-
I have this problem too. Any updates? |
Beta Was this translation helpful? Give feedback.
-
Is this relevant? |
Beta Was this translation helpful? Give feedback.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
-
Please let us know if |
Beta Was this translation helpful? Give feedback.
-
@knqyf263 in this case that variable did not help, it was the |
Beta Was this translation helpful? Give feedback.
-
Seems like it’s more complicated than that.
…On Tue, Feb 14, 2023 at 6:50 AM Mitch Murphy ***@***.***> wrote:
@knqyf263 <https://github.com/knqyf263> in this case that variable did
not help, it was the seLinux flags
—
Reply to this email directly, view it on GitHub
<#3170 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACQLGLUNE7AUYSYT7O7EDBLWXNWQZANCNFSM6AAAAAAR6P6REY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Description
I am trying to scan all images deployed on my EKS cluster I am setting up for high security (will be deployed to classified IL5 environment). Kubernetes v1.23, all worker nodes run on Bottlerocket OS.
What did you expect to happen?
I expect images to be scanned and available in the VulnerabilityReports CRD
What happened instead?
I was able to successfully install Falco to the cluster (uses containerd). However, when deploying the official Helm chart (0.6.0-rc3) the scan-vulnerability containers start and then immediately error out. I set this environment variable on the trivy-operator deployment:
Output of run with
-debug
:I added the following security context:
Beta Was this translation helpful? Give feedback.
All reactions