Skip to content
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

gcb build fails with error "no token in bearer response" #577

Closed
ahmetb opened this issue May 23, 2018 · 0 comments · Fixed by #579
Closed

gcb build fails with error "no token in bearer response" #577

ahmetb opened this issue May 23, 2018 · 0 comments · Fixed by #579

Comments

@ahmetb
Copy link
Contributor

ahmetb commented May 23, 2018

Expected behavior

Expected gcb build to succeed.

Actual behavior

skaffold run -p gcb failed with:

Starting build...
Pushing code to gs://ahmetb-samples-playground_cloudbuild/source/ahmetb-samples-playground-ca35b247501effa57363177b177c96a3.tar.gz
Logs at available at
https://console.cloud.google.com/m/cloudstorage/b/ahmetb-samples-playground_cloudbuild/o/log-ece1a498-f18f-4852-b310-84759e9ab0e5.txt
starting build "ece1a498-f18f-4852-b310-84759e9ab0e5"

FETCHSOURCE
Fetching storage object: gs://ahmetb-samples-playground_cloudbuild/source/ahmetb-samples-playground-ca35b247501effa57363177b177c96a3.tar.gz#1527063127212050
Copying gs://ahmetb-samples-playground_cloudbuild/source/ahmetb-samples-playground-ca35b247501effa57363177b177c96a3.tar.gz#1527063127212050...
/ [1 files][ 24.3 MiB/ 24.3 MiB]
Operation completed over 1 objects/24.3 MiB.
BUILD
Already have image (with digest): gcr.io/cloud-builders/docker
Sending build context to Docker daemon  177.4MB
Step 1/9 : FROM golang:1.10-alpine AS build
1.10-alpine: Pulling from library/golang
ff3a5c916c92: Already exists
1a649ea86bca: Already exists
ce35f4d5f86a: Already exists
7db6b75ae47d: Already exists
fc46bec5ec29: Already exists
Digest: sha256:9de80ce12179b571ed46f9d1fb12261640a6d5af04689d6536a07f9dc23eae50
Status: Downloaded newer image for golang:1.10-alpine
 ---> 05fe62871090
Step 2/9 : RUN apk add --no-cache git ca-certificates
 ---> Running in 20182a86d184
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/community/x86_64/APKINDEX.tar.gz
(1/5) Installing libssh2 (1.8.0-r2)
(2/5) Installing libcurl (7.60.0-r0)
(3/5) Installing expat (2.2.5-r0)
(4/5) Installing pcre2 (10.30-r0)
(5/5) Installing git (2.15.0-r1)
Executing busybox-1.27.2-r7.trigger
OK: 19 MiB in 17 packages
Removing intermediate container 20182a86d184
 ---> 91d2cc4c1e78
Step 3/9 : COPY . ./src/github.com/ahmetb/gkedns
 ---> f0a98bdcb4ed
Step 4/9 : RUN go install github.com/ahmetb/gkedns/cmd/cluster-registry-web
 ---> Running in 278f16cba547
Removing intermediate container 278f16cba547
 ---> 04e9b214592c
Step 5/9 : FROM alpine
latest: Pulling from library/alpine
Digest: sha256:8c03bb07a531c53ad7d0f6e7041b64d81f99c6e493cb39abba56d956b40eacbc
Status: Downloaded newer image for alpine:latest
 ---> 3fd9065eaf02
Step 6/9 : RUN apk add --no-cache git ca-certificates
 ---> Running in f8bcb61d398d
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/community/x86_64/APKINDEX.tar.gz
(1/6) Installing ca-certificates (20171114-r0)
(2/6) Installing libssh2 (1.8.0-r2)
(3/6) Installing libcurl (7.60.0-r0)
(4/6) Installing expat (2.2.5-r0)
(5/6) Installing pcre2 (10.30-r0)
(6/6) Installing git (2.15.0-r1)
Executing busybox-1.27.2-r7.trigger
Executing ca-certificates-20171114-r0.trigger
OK: 19 MiB in 17 packages
Removing intermediate container f8bcb61d398d
 ---> 9b114dc535d1
Step 7/9 : COPY --from=build /go/bin/cluster-registry-web /bin/cluster-registry-web
 ---> 003b90fa5454
Step 8/9 : ENTRYPOINT ["/bin/cluster-registry-web"]
 ---> Running in 5f45083150c2
Removing intermediate container 5f45083150c2
 ---> 7c883b36259b
Step 9/9 : EXPOSE 8080
 ---> Running in 9b163e294e61
Removing intermediate container 9b163e294e61
 ---> d46191d90063
Successfully built d46191d90063
Successfully tagged gcr.io/ahmetb-samples-playground/cluster-registry-web:latest
PUSH
Pushing gcr.io/ahmetb-samples-playground/cluster-registry-web
The push refers to repository [gcr.io/ahmetb-samples-playground/cluster-registry-web]
ff9405c80ff7: Preparing
ea8e733c944f: Preparing
cd7100a72410: Preparing
cd7100a72410: Layer already exists
ea8e733c944f: Pushed
ff9405c80ff7: Pushed
latest: digest: sha256:b1f43a7406f8aeb5120170b5b655311dfc826aae505686fff32100df59ae25c0 size: 951
DONE
Error: build: build step: building artifact gcr.io/ahmetb-samples-playground/cluster-registry-web: tagging image: no token in bearer response:
{"errors":[{"code":"UNKNOWN","message":"Malformed scope: \"push,pull\"."}]}
Usage:
  skaffold run [flags]

Flags:
  -f, --filename string       Filename or URL to the pipeline file (default "skaffold.yaml")
  -h, --help                  help for run
  -p, --profile stringArray   Activate profiles by name
  -t, --tag string            The optional custom tag to use for images which overrides the current Tagger configuration
      --toot                  Emit a terminal beep after the deploy is complete

Global Flags:
  -v, --verbosity string   Log level (debug, info, warn, error, fatal, panic (default "warning")

Information

Steps to reproduce the behavior

  1. skaffold run -p gcb
jonjohnsonjr added a commit to jonjohnsonjr/skaffold that referenced this issue May 23, 2018
Fixes GoogleContainerTools#577. This was introduced by GoogleContainerTools#548.

This is go-containerregistry leaking a bit too much detail that we
should fix upstream.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant