From d0d29d9ff0702cd5f085a95a93a278088c461f71 Mon Sep 17 00:00:00 2001 From: O'meid Date: Fri, 1 Feb 2019 10:05:33 +1100 Subject: [PATCH] containers/images: clarify dockercfg limitions. (#12429) Related #59406 This commit clarifies the limitations of dockercfg use by Kubernetes, specifically, the lack of support for credential helpers. --- content/en/docs/concepts/containers/images.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/content/en/docs/concepts/containers/images.md b/content/en/docs/concepts/containers/images.md index 07e9752fcc..8885784e4c 100644 --- a/content/en/docs/concepts/containers/images.md +++ b/content/en/docs/concepts/containers/images.md @@ -170,6 +170,11 @@ will not work reliably on GCE, and any other cloud provider that does automatic node replacement. {{< /note >}} +{{< note >}} +Kubernetes as of now only supports the `auths` and `HttpHeaders` section of docker config. This means credential helpers (`credHelpers` or `credsStore`) are not supported. +{{< /note >}} + + Docker stores keys for private registries in the `$HOME/.dockercfg` or `$HOME/.docker/config.json` file. If you put the same file in the search paths list below, kubelet uses it as the credential provider when pulling images.