Closed anujkaushal closed 3 weeks ago
Hi @anujkaushal you can't do this from a running container, you need to recreate your controller image by updating the docker file and regenerating. Something like the below:
FROM quay.io/operator-framework/helm-operator
USER root
RUN microdnf update && microdnf clean all
# anything else needed
I hope this helps.
Thanks @acornett21
Bug Report
I am trying to fix CVE by running
microdnf update
andmicrodnf upgrade
but it's throwing error.What did you do?
Pulled the latest helm-operator image from the quay.io - helm-operator container repository. Inside the container i tried to update and upgrade packages but it didn't work and throws error mentioned below.
What did you expect to see?
I want to helm-operator image to be able to run update and upgrade to fix CVEs.
What did you see instead? Under which circumstances?
While try to debug the problem i have tried to create that folder path manually from the error message. But it required root permission.
Also it seems sudo is not install.
Environment
Operator SDK v1.31.1 Operator K8s version: 1.28
Operator type: Helm Based Operator
/language helm
Kubernetes cluster type:
AWS EKS
$ operator-sdk version
$ kubectl version
Possible Solution
Additional context