-
Notifications
You must be signed in to change notification settings - Fork 31
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
fix: container has runAsNonRoot and image will run as root #252
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: googs1025 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-node-feature-discovery-operator-build-gh-pages |
Not sure why ci reports an error... 🤔 |
Thank you @googs1025
Argh, it's the jekyll-rtd-theme 🤯 We need to port this kubernetes-sigs/node-feature-discovery#1829 to make the documentation buildable again |
/lgtm |
@marquiz @yevgeny-shnaidman this is ready for next! |
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this problem only affects the release-0.6 branch (that's what you were deploying)? So if we make changes in master
that should be then backported to release-0.6
@@ -27,7 +27,6 @@ spec: | |||
- name: manager | |||
securityContext: | |||
readOnlyRootFilesystem: true | |||
runAsNonRoot: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is not the right fix. We shouldn't need to run the image as root.
Instead add:
runAsUser: 65534
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Warning Failed 76s (x7 over 2m25s) kubelet Error: container has runAsNonRoot and image will run as root (pod: "nfd-controller-manager-6658568db5-2fdrm_node-feature-discovery-operator(869ad52b-d4ae-4314-a69b-4d7faa8148da)", container: manager)
I made the change based on the error, which is a bit weird. Ok, I will try this approach this weekend. 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NP. The default user in the image is root (uid 0), not great choice by itself. You can override that with runAsUser
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
New changes are detected. LGTM label has been removed. |
install problem: