Error deploying with gcr.io/paketo-buildpacks/go

Questions / Help Build debugging
1

Following the instructions on

results in an almost immediate build error:

==> Verifying app config
--> Verified app config
==> Building image
==> Building image with Buildpacks
--> docker host: 20.10.12 linux x86_64
base: Pulling from paketobuildpacks/builder
Digest: sha256:fae8256cac2619dee47de12eef605c10df2efe8dcb03aa00da795c895a9d38fc
Status: Image is up to date for paketobuildpacks/builder:base
base-cnb: Pulling from paketobuildpacks/run
Digest: sha256:41ea15b4d591c2722543009fbf8267a13019ecdc8c6a2b4f437ed83ed29bf72c
Status: Image is up to date for paketobuildpacks/run:base-cnb
Error failed to fetch an image or build from source: downloading buildpack: extracting from registry gcr.io/paketo-buildpacks/go: fetching image: resolve auth for ref gcr.io/paketo-buildpacks/go: error getting credentials - err: exec: "docker-credential-gcloud": executable file not found in $PATH, out: ``
2

Hi,

This answer will be a hit or miss…

... fetching image: resolve auth for ref gcr.io/paketo-buildpacks/go: error getting credentials - err: exec: "docker-credential-gcloud": executable file not found in $PATH, out: ``

You may have to install docker-credential-gcloud on your machine (and make sure it adds itself in the $PATH).

Ref: Last few comments from this thread.

3

Huh! Interesting. Can confirm I had to install the gcloud tooling and now things are working. I’ve deployed go apps on fly a lot recently. Not sure what changed recently.

Thanks @FrequentFlyer!

4

Thanks for confirming :+1:
Old man yells at cloud is valid after all.

I still don’t know (& haven’t searched the forum to find) what is attempted first - local or remote.
If remote build also fails with this error, Fly’s builder VM will probably need this added as well (if that fails with the same error).