使用 kubeadm(kubernetes) 时 google-containers 和 google_containers 有什么区别
what's the difference between google-containers and google_containers when use kubeadm(kubernetes)
目前我正在使用 kubeadm 1.7.2 安装 kubernetes。
它将下载像 gcr.io/google_containers/etc-amd64:3.0.17 这样的图像。
但是在gcr.io里，我只看到google-containers.
所以gcr.io.google_containers是一样的gcr.io.google-containers????
如果它们相同，为什么当我将它们标记为 google-containers 而不是 google-containers 时，kubeadm 将下载 google_containers/xxx ???
So gcr.io.google_containers is the same gcr.io.google-containers
自 2015 年以来，是：参见 kubernetes issue 6229
It turns out that that is because I am using an older version of docker which does not allow "-" in namespaces.
I get Invalid namespace name (google-containers), only [a-z0-9_] are allowed, size between 4 and 30 error on running $docker pull gcr.io/google-containers/heapster.
@thockin suggested that we can change the path to use google_containers instead of google-containers since that works for all versions of docker.
目前我正在使用 kubeadm 1.7.2 安装 kubernetes。
它将下载像 gcr.io/google_containers/etc-amd64:3.0.17 这样的图像。
但是在gcr.io里，我只看到google-containers.
所以gcr.io.google_containers是一样的gcr.io.google-containers????
如果它们相同，为什么当我将它们标记为 google-containers 而不是 google-containers 时，kubeadm 将下载 google_containers/xxx ???
So gcr.io.google_containers is the same gcr.io.google-containers
自 2015 年以来，是：参见 kubernetes issue 6229
It turns out that that is because I am using an older version of docker which does not allow "
-" in namespaces.
I getInvalid namespace name (google-containers), only [a-z0-9_] are allowed, size between 4 and 30error on running$docker pull gcr.io/google-containers/heapster.@thockin suggested that we can change the path to use
google_containersinstead ofgoogle-containerssince that works for all versions of docker.