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

kubelet does not read ~/.docker/config.json if it is created after it is started #69637

Open
mitar opened this Issue Oct 10, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@mitar
Contributor

mitar commented Oct 10, 2018

/kind feature

What happened:

Based on my testing, if I do docker login after kubelet is already running on the node, pulling private images fails even if ~/.docker/config.json now exists.

What you expected to happen:

I would expect that I can pull private images after I run docker login and when the ~/.docker/config.json file exists, no matter if kubelet is already running or not.

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

  • Have a cluster and node running.
  • Run docker login on your node.
  • Create a pod using an image from the private repository.
  • Observe that pulling the image fails.

Anything else we need to know?:

I am trying to achieve what is documented here. I do not see anywhere in documentation that kubelet should be started after this file exists, or restarted for its content to be picked up.

Environment:

  • Kubernetes version (use kubectl version): v1.11.3
  • Cloud provider or hardware configuration: custom server
  • OS (e.g. from /etc/os-release): Ubuntu 17.10
  • Kernel (e.g. uname -a): 4.4.0-121-generic #145-Ubuntu SMP Fri Apr 13 13:47:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
@mitar

This comment has been minimized.

Show comment
Hide comment
@mitar

mitar Oct 10, 2018

Contributor

cc @kubernetes/sig-node-feature-requests

Contributor

mitar commented Oct 10, 2018

cc @kubernetes/sig-node-feature-requests

@k8s-ci-robot k8s-ci-robot added sig/node and removed needs-sig labels Oct 10, 2018

@k8s-ci-robot

This comment has been minimized.

Show comment
Hide comment
@k8s-ci-robot

k8s-ci-robot Oct 10, 2018

Contributor

@mitar: Reiterating the mentions to trigger a notification:
@kubernetes/sig-node-feature-requests

In response to this:

cc @kubernetes/sig-node-feature-requests

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.

Contributor

k8s-ci-robot commented Oct 10, 2018

@mitar: Reiterating the mentions to trigger a notification:
@kubernetes/sig-node-feature-requests

In response to this:

cc @kubernetes/sig-node-feature-requests

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment