From fb1432264182baa52e89c1b8eb593f1074e66e06 Mon Sep 17 00:00:00 2001 From: Andrey Chernih Date: Thu, 11 Jan 2018 16:07:23 -0800 Subject: [PATCH] Added notes on how to fix pulling errors Getting this error when running `helm init` locally: Failed to pull image "gcr.io/kubernetes-helm/tiller:v2.7": rpc error: code = Unknown desc = Error response from daemon: manifest for gcr.io/kubernetes-helm/tiller:v2.7 not found --- docs/developers.md | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/docs/developers.md b/docs/developers.md index ec0b9f91b..f6261248d 100644 --- a/docs/developers.md +++ b/docs/developers.md @@ -87,7 +87,19 @@ GCR registry. For development, we highly recommend using the [Kubernetes Minikube](https://github.com/kubernetes/minikube) developer-oriented distribution. Once this is installed, you can use -`helm init` to install into the cluster. +`helm init` to install into the cluster. Note that version of tiller you're using for +development may not be available in Google Cloud Container Registry. If you're getting +image pull errors, you can override the version of Tiller. Example: + +```console +helm init --tiller-image=gcr.io/kubernetes-helm/tiller:2.7.2 +``` + +Or use the latest version: + +```console +helm init --canary-image +``` For developing on Tiller, it is sometimes more expedient to run Tiller locally instead of packaging it into an image and running it in-cluster. You can do @@ -129,7 +141,7 @@ The code for the Helm project is organized as follows: - The individual programs are located in `cmd/`. Code inside of `cmd/` is not designed for library re-use. - Shared libraries are stored in `pkg/`. -- The raw ProtoBuf files are stored in `_proto/hapi` (where `hapi` stands for +- The raw ProtoBuf files are stored in `_proto/hapi` (where `hapi` stands for the Helm Application Programming Interface). - The Go files generated from the `proto` definitions are stored in `pkg/proto`. - The `scripts/` directory contains a number of utility scripts. Most of these