emissary-ingress / emissary

open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
https://www.getambassador.io
Apache License 2.0
4.36k stars 684 forks source link

local make push to private repo fails on Building image emissary #3707

Closed yawboateng closed 3 years ago

yawboateng commented 3 years ago

Im unable to build locally and push to a private repo. I'm login to my private repo and exported it as the DEV_REGISTRY but there seem to be a step to pull from docker hub with error:

#3 [internal] load metadata for docker.io/library/sha256:b2b9b741de516811541c2d580129b50500e83ae1fa9d11e13e2ddc12db43c3c7
#3 sha256:d634e408ca4c714e101e64390b0a1f846e9cfb31ca6602c1420d062da3527382
#3 ERROR: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

full log:

make push       
BUILDER_NAME=emissary /Users/yawboateng/Documents/devSpace/emissary/builder/builder.sh raw-version > python/ambassador.version
==> Base Envoy image is already pulled
printf '%s\n' $(cat docker/base-envoy.docker) emissary.local/base-envoy | /Users/yawboateng/Documents/devSpace/emissary/build-aux/bin/write-dockertagfile docker/base-envoy.docker.tag.local
==> Preflight checks
Checking that 'rsync' is installed and is new enough to support '--info'
Checking that 'go' is installed and is 1.13 or later
Checking that 'docker' is installed and supports the 'slice' function for '--format'
==> Bootstrapping builder base image
  -> Using stage-1 base gcr.io/<repo>/builder-base:stage1-20210815x7-3577b8aaf78445fa
  -> Using stage-2 base gcr.io/<repo>/builder-base:stage2-20210815x7-3577b8aaf78445fa-64c7e58a1faaa3e0
==> Building image emissary
    envoy=sha256:b2b9b741de516811541c2d580129b50500e83ae1fa9d11e13e2ddc12db43c3c7
    builderbase=gcr.io/<repo>/builder-base:stage2-20210815x7-3577b8aaf78445fa-64c7e58a1faaa3e0
#1 [internal] load build definition from Dockerfile
#1 sha256:cef17b63e7eb8da8a2c7c2c541415442cef275fea001d17cf8cd487960a0af84
#1 transferring dockerfile: 37B done
#1 DONE 0.0s

#2 [internal] load .dockerignore
#2 sha256:7ac48827b8214a9077c11de126ff17b8ba182c86dea29e545cbd0681e5f2390f
#2 transferring context: 35B done
#2 DONE 0.0s

#4 [internal] load metadata for gcr.io/<repo>/builder-base:stage2-20210815x7-3577b8aaf78445fa-64c7e58a1faaa3e0
#4 sha256:0a02ddcb0fda076b8586016856e4644cda579672b5979a843e66a06a5ab6494e
#4 DONE 0.0s

#5 [internal] load metadata for docker.io/frolvlad/alpine-glibc:alpine-3.12_glibc-2.32
#5 sha256:40158a9a498f332ba9bbb5a3e512d0ad5c79a4ac03de6c84a0a9854ca34f9e6a
#5 DONE 0.3s

#3 [internal] load metadata for docker.io/library/sha256:b2b9b741de516811541c2d580129b50500e83ae1fa9d11e13e2ddc12db43c3c7
#3 sha256:d634e408ca4c714e101e64390b0a1f846e9cfb31ca6602c1420d062da3527382
#3 ERROR: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
------
 > [internal] load metadata for docker.io/library/sha256:b2b9b741de516811541c2d580129b50500e83ae1fa9d11e13e2ddc12db43c3c7:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
isaac88 commented 3 years ago

I have the same issue @yawboateng

Did you finally solve it ?

Thanks

yawboateng commented 3 years ago

nope, its still an issue

aidanhahn commented 3 years ago

A workaround for this is to export DOCKER_BUILDKIT=0

yawboateng commented 3 years ago

Thanks @aidanhahn ... that worked

efunk commented 3 years ago

Fix released in Edge Stack 2.0.3 EA.