-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Fixes reading /root/.docker/config.json on debian #3198
Fixes reading /root/.docker/config.json on debian #3198
Conversation
Debian and probably others apparently don't automatically default to using the root account if it's not specified.
Hi @blakebarnett. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/assign @justinsb |
/ok-to-test Who does the systemd service run as without this @blakebarnett ? I did notice that HOME was not set correctly on systemd - I wonder if that is the problem. But maybe setting this has the effect of setting HOME? |
So running stuff as root always gives me a chill down my spine. Shouldn't we have a privileged kubernetes user that is running kubelet? |
It's a good idea, but adds user management across all supported OSes into the mix... |
@justinsb I haven't verified but I believe it's |
I checked on CoreOS & Debian and it looks like it runs as root without the env. I like making it explicit therefore (so we know to consider changing the user later), and the "side-effect" of getting the env is great! /lgtm /ok-to-test |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: blakebarnett, justinsb The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/retest |
Test failure filed as kubernetes/kubernetes#51429 |
/retest |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
Ah that makes more sense. 👍 |
Debian and probably others apparently don't automatically default to using the root account if it's not specified.
ref: kubernetes/kubernetes#45487 (comment)