insufficient_scope: authorization failed #160

AntonioFalcaoJr · 2020-10-05T02:30:24Z

Behaviour

Steps to reproduce this issue

Set up QEMU
Set up Docker Buildx
Login to DockerHub
Build and push

Expected behaviour

Publish image to docker hub

Actual behaviour

ERROR: server message: insufficient_scope: authorization failed

Configuration

https://github.com/AntonioFalcao/Dotnet5.GraphQL3.WebApplication
https://hub.docker.com/repository/docker/antoniofalcaojr/dotnet5-graphql3-webapi

name: Push API Image

on:
  push:
    branches: master
  workflow_dispatch:

jobs:
  push_to_registry:
    name: Push Docker image to Docker Hub
    runs-on: ubuntu-latest
    steps:
      -
        name: Set up QEMU
        uses: docker/setup-qemu-action@v1
      -
        name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1
      -
        name: Login to DockerHub
        uses: docker/login-action@v1 
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}
      -
        name: Build and push
        id: docker_build
        uses: docker/build-push-action@v2
        with:
          file: ./src/Dotnet5.GraphQL3.Store.WebAPI/Dockerfile 
          push: true
          tags: antoniofalcaojf/dotnet5-graphql3-webapi:latest
      -
        name: Image digest
        run: echo ${{ steps.docker_build.outputs.digest }}

Command produced

/usr/bin/docker buildx build --tag antoniofalcaojf/dotnet5-graphql3-webapi:latest --iidfile /tmp/docker-build-push-lDmUS3/iidfile --secret id=GIT_AUTH_TOKEN,src=/tmp/docker-build-push-lDmUS3/tmp-3384-twk4xwQeuxwk --file ./src/Dotnet5.GraphQL3.Store.WebAPI/Dockerfile --push https://github.com/AntonioFalcao/Dotnet5.GraphQL3.WebApplication.git#heads/release

Logs

#33 exporting to image
#33 exporting layers
#33 exporting layers 2.4s done
#33 exporting manifest sha256:3c6a2a955932783e726461031bee8657c2ec7f2b2f239c110ba44ae58effef69 done
#33 exporting config sha256:6d39eefff02cee7c50511f16bd824957f3ef082ed60324850954a5aa3b13a5ee done
#33 pushing layers
#33 pushing layers 0.2s done
#33 ERROR: server message: insufficient_scope: authorization failed
------
 > exporting to image:
------
failed to solve: rpc error: code = Unknown desc = server message: insufficient_scope: authorization failed
Error: The process '/usr/bin/docker' failed with exit code 1

The text was updated successfully, but these errors were encountered:

socheatsok78 · 2020-10-05T03:40:44Z

I'm having the same issues!

crazy-max · 2020-10-05T10:06:06Z

@antoniofalcao Looks like the same issue as #162 when Git context is used. Can you use the Path context while waiting for a fix?:

name: Push API Image

on:
  push:
    branches: master
  workflow_dispatch:

jobs:
  push_to_registry:
    name: Push Docker image to Docker Hub
    runs-on: ubuntu-latest
    steps:
      -
        name: Checkout
        uses: actions/checkout@v2
      -
        name: Set up QEMU
        uses: docker/setup-qemu-action@v1
      -
        name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1
      -
        name: Login to DockerHub
        uses: docker/login-action@v1 
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}
      -
        name: Build and push
        id: docker_build
        uses: docker/build-push-action@v2
        with:
          context: .
          file: ./src/Dotnet5.GraphQL3.Store.WebAPI/Dockerfile 
          push: true
          tags: antoniofalcaojf/dotnet5-graphql3-webapi:latest
      -
        name: Image digest
        run: echo ${{ steps.docker_build.outputs.digest }}

socheatsok78 · 2020-10-05T10:40:38Z

Yes adding context: . fix the problem.

AntonioFalcaoJr · 2020-10-05T12:13:25Z

Thank's @crazy-max, but i already used this approach, and had the same error.

Applying suggestion

name: Push API Image

on:
  push:
    branches: master
  workflow_dispatch:

jobs:
  push_to_registry:
    name: Push Docker image to Docker Hub
    runs-on: ubuntu-latest
    steps:
      -
        name: Checkout
        uses: actions/checkout@v2
      -
        name: Set up QEMU
        uses: docker/setup-qemu-action@v1
      -
        name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v1
      -
        name: Login to DockerHub
        uses: docker/login-action@v1 
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}
      -
        name: Build and push
        id: docker_build
        uses: docker/build-push-action@v2
        with:
          context: .
          file: ./src/Dotnet5.GraphQL3.Store.WebAPI/Dockerfile 
          push: true
          tags: antoniofalcaojf/dotnet5-graphql3-webapi:latest
      -
        name: Image digest
        run: echo ${{ steps.docker_build.outputs.digest }}

Command produced

/usr/bin/docker buildx build --tag antoniofalcaojf/dotnet5-graphql3-webapi:latest --iidfile /tmp/docker-build-push-xwP62S/iidfile --file ./src/Dotnet5.GraphQL3.Store.WebAPI/Dockerfile --push .

Logs

#35 exporting to image
#35 exporting layers
#35 exporting layers 2.2s done
#35 exporting manifest sha256:a506612326c0df77c685c8ae913ca22ddb0da48dbb9a74dc8eface5c8ec96b6e
#35 exporting manifest sha256:a506612326c0df77c685c8ae913ca22ddb0da48dbb9a74dc8eface5c8ec96b6e done
#35 exporting config sha256:8508a57b7ee75695eddb38cd79e53398cf12fb5e789a0bf7c9d00a81d5367649 done
#35 pushing layers
#35 pushing layers 0.2s done
#35 ERROR: server message: insufficient_scope: authorization failed
------
 > exporting to image:
------
failed to solve: rpc error: code = Unknown desc = server message: insufficient_scope: authorization failed
Error: The process '/usr/bin/docker' failed with exit code 1

Any suggestion?

crazy-max · 2020-10-05T13:02:02Z

@antoniofalcao Looks like antoniofalcaojf/dotnet5-graphql3-webapi is missing on Docker Hub. Is it a private repo?

AntonioFalcaoJr · 2020-10-05T13:12:18Z

@antoniofalcao Looks like antoniofalcaojf/dotnet5-graphql3-webapi is missing on Docker Hub. Is it a private repo?

It's public: https://hub.docker.com/repository/docker/antoniofalcaojr/dotnet5-graphql3-webapi

crazy-max · 2020-10-05T13:15:15Z

@antoniofalcao So it's a typo in your workflow:

antoniofalcaojf/dotnet5-graphql3-webapi != antoniofalcaojr/dotnet5-graphql3-webapi

AntonioFalcaoJr · 2020-10-05T13:23:06Z

@antoniofalcao So it's a typo in your workflow:

antoniofalcaojf/dotnet5-graphql3-webapi != antoniofalcaojr/dotnet5-graphql3-webapi

OMG! So sorry about that! It's working now. Thanks!

docker/build-push-action#160

See docker/build-push-action#160

* testing docker from github * minor fix to travis-ci * changed branch to $TRAVIS_BRANCH * adding env variables * adding env variables * double checking that travis variables are set up * double checking that travis variables are set up * double checking that travis variables are set up * changing from deploy tag to after_success tag * lowercase slug * trying to fix the build tag name * trying to fix the build tag name * chewbbaca with python3 * chewbbaca with python3 * debugging docker tag * debugging docker tag * debugging docker tag * debugging docker tag * debugging docker tag * debugging docker tag * fixing docker tag * fixing docker login * explicitly giving lskatz for username * secret variable space * trying to get secret env variables for docker login * trying out docker caching * Update .travis.yml * fix "docker save" * trying the other kind of caching * fixed single quote * view dockerImages.stdout * added cache folder * test for size of dockerImages.stdout * from xargs to bash loop * fixed a quote * a quick rm cache * Update .travis.yml * after removing all cache * rm cache * checking if file exists * rm cache * back to normal * Create travis-docker.yml * Update travis-docker.yml * Update travis-docker.yml * docker login * passwordless login * docker build * updating run commands for variable printing * updating run commands for variable printing * updating run commands for variable printing * more debugging; switching build directory to HOME * more debugging * more debugging * more debugging * actions/checkout@v2 * actions/checkout on this branch * actions/checkout on this branch * actions/checkout on this branch * actions/checkout on this branch * fixed space typo * fixed working directory during docker build * fixed working directory during docker build * fixing docker build * fixing docker build * fixing docker build * fixing docker build * fixing docker build * trying docker push * using a more appropriate env variable * fixed case on docker tag * moving env out of job and to global * separating out to multiple jobs that depend on each other, in preparation for any concurrency * some concurrency * m * m * added some debugging * m * added init and debugging jobs * init needs debugging * exporting REMOTE_TAG * figuring out variable continuity * figuring out variable continuity * passing outputs between jobs * passing outputs between jobs * passing outputs between jobs * debugging more * debugging more * debugging more with JSON * debugging more with JSON * debugging more with JSON2 * moved git checkout to init job * maybe I needed to do fromJSON. And moved git checkout back. * JSON3 * JSON3 * JSON4 * JSON5 * JSON6 * test slug * removed all underscores and dashes in this output chain * export slug * export slug2 * just trying to make env work at all * env2 * env3 * making the env work properly with format() * env2 * env3 * env4 * env5 * env6 * trying things out * trying things out * trying things out * trying things out * trying things out * just making the variables work * docker cache action * docker cache action * Trying to follow satackey more closely * Update travis-docker.yml * added docker login * login before tagging * Rename travis-docker.yml to travis-docker.yml.bak * Create github-docker.yml * removed needs:init * corrected the docker repo * pushing to both docker and github https://docs.github.com/en/actions/guides/publishing-docker-images * renamed the github container name from my-image to sneakernet * tags: latest * adding extra LC_ALL to the end * newer blast in Dockerfile * blast library COPY statements * reverting blast libs * getting blast from mlst container * manual installation of staramr * manual installation of staramr2 * tag with hashsum values too * trying to invoke the sha sum * adding apt-get packages for staramr * trying out docker push v2 * trying docker action v2 * fixed newline error * removed ipython-notebook * Update github-docker.yml * Update Dockerfile * numpy installation through pip now * Removing multistage for pip-based images * fixed apt-get command syntax * changed tags to a value instead a list * updated the tag docker/build-push-action#160 * list of tags * pushing to the github registry (?) * one space before pipe * Not sending to github packages; yes sending multiple tags to dockerhub * removed list again * Rename github-docker.yml to github-docker.yml.bak * Create build-and-push-container.yml * added this branch for github actions * added libpython3.5-dev ``` #130 [linux/386 stage-11 34/47] RUN pip3 install poetry && git clone https:/... #130 11.73 building '_openssl' extension #130 11.73 creating build/temp.linux-x86_64-3.6/build #130 11.73 creating build/temp.linux-x86_64-3.6/build/temp.linux-x86_64-3.6 #130 11.73 i686-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.6m -c build/temp.linux-x86_64-3.6/_openssl.c -o build/temp.linux-x86_64-3.6/build/temp.linux-x86_64-3.6/_openssl.o -Wconversion -Wno-error=sign-conversion #130 11.73 build/temp.linux-x86_64-3.6/_openssl.c:50:14: fatal error: pyconfig.h: No such file or directory #130 11.73 # include <pyconfig.h> #130 11.73 ^~~~~~~~~~~~ #130 11.73 compilation terminated. #130 11.73 error: command 'i686-linux-gnu-gcc' failed with exit status 1 #130 11.73 ---------------------------------------- #130 11.73 ERROR: Failed building wheel for cryptography #130 11.73 Failed to build cryptography #130 11.74 ERROR: Could not build wheels for cryptography which use PEP 517 and cannot be installed directly #130 ERROR: executor failed running [/bin/sh -c pip3 install poetry && git clone https://github.com/hcdenbakker/SalmID.git --branch 0.1.23 --single-branch && cd SalmID && poetry build -vvv && pip3 install dist/salmid*.whl]: buildkit-runc did not terminate successfully ``` * fixed libpython-dev * libpython3-dev * newline. Does it make things work * separate some pip3 installations for staramr; removed numpy pip3 * removing staramr and salmid for right now * removed all platforms except linux/amd64 * uncomment pip commands * combined some pip commands for fewer layers * Combined some chewbbaca steps into single layers * RUN echo "LC_ALL=C" >> /etc/environment * switched to UTF-8 per instructions * apt-get install locales Co-authored-by: Lee Katz - Aspen <[email protected]>

chase-moskal · 2021-06-29T06:23:51Z

hello, if anybody else gets stuck on this like i did, here's what i did to solve it

i had to fix my tags setting:

    - name: push image - server
      uses: docker/build-push-action@v2
      with:
        file: ./s/Dockerfile
        context: .
        push: true
        tags: ${{ env.REGISTRY }}/${{ github.repository }}/server:${{ github.sha }}

where

${{ env.REGISTRY }} is equivalent with ghcr.io (the github packages registry)
${{ github.repository }} is equivalent with chase-moskal/xiome (my github name and private repo's name)
server is the name i decided for my docker image, since my repo is pushing multiple different images
${{ github.sha }} is simply the commit id, which i'm using to identify my staging images (i plan to use git v tags for real production releases)
thus it computes to something like ghcr.io/chase-moskal/xiome/server:69aa49cd2994f2063f908dd8868f1aa4da2385bddfbc0e069534a7fa5865cb08

this fixed the issue in my case, particularly adding the ghcr.io/ prefix

pffont · 2022-03-23T19:21:56Z

Hello,

If someone is having the same issue, the solution for me was push to a new repository:

- name: push image - server
      uses: docker/build-push-action@v2
      with:
        push: true
        tags: myuser/new_repository/imagename:tag

Drallas · 2022-04-19T16:25:05Z

I had this too, make sure myuser is set to you real docker username; that's what caused my Action to fail!

philipzimmermann · 2022-05-09T20:11:38Z

For me the problem was that I had to login in Docker on the command line:
docker login --username=<username>

lclarkg18 · 2022-06-02T23:14:06Z

I had this too, make sure myuser is set to you real docker username; that's what caused my Action to fail!

Hiding in plain sight!! Thanks a million! It was just changing user for me though, but same line

docker/build-push-action#160

Recommended by docker/build-push-action#160

moofoo · 2022-10-29T23:31:20Z

Strangely enough, I was getting this error because of a mismatch between the name given to a build stage and the name used in a COPY --from=... instruction. I fortunately stumbled on this answer, which got me looking at the FROM and COPY instructions in my Dockerfile.

I feel like incongruencies between build stage names in FROM and COPY instructions could probably be caught by syntax validation before cascading, somehow, to an auth failure.

Hope this helps somebody, I spent way too much time on this snafu.

Trying to make dockerhub publishing work with inspiration from this example: https://docs.docker.com/build/ci/github-actions/multi-platform/ * Set `with.context: .` * bump step versions It fails with the following error ``` insufficient_scope: authorization failed ``` Which led me to this thread: docker/build-push-action#160

ummae · 2024-02-10T08:56:02Z

Hi, I have a similar problem but none of above solutions works for me. In my case, docker/metadata-action cause the same error following:

Error: buildx failed with: ERROR: failed to solve: failed to push latest: server message: insufficient_scope: authorization failed

Orignal workflow(error):

    runs-on: [self-hosted, cpu]
    steps:
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v2
      - name: Login to Docker Hub
        uses: docker/login-action@v2
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}
      - name: Docker meta
        id: meta
        uses: docker/metadata-action@v5
        with:
          tags: type=match,pattern=v(.*),group=1
...

Moving docker/metadata-action before docker/login-action shows silightly different error:

    steps:
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v2
      - name: Docker meta
        id: meta
        uses: docker/metadata-action@v5
        with:
          tags: type=match,pattern=v(.*),group=1
      - name: Login to Docker Hub
        uses: docker/login-action@v2
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}
...

buildx failed with: ERROR: failed to solve: failed to push latest: push access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

It works without a docker/metadata-action step.

docker/build-push-action:

      - name: Build and push
        uses: docker/build-push-action@v3
        with:
          push: true
          context: dockerfiles/mod/
          file: dockerfiles/mod/Dockerfile.base
          target: runtime-image
          cache-from: type=gha
          cache-to: type=gha,mode=max
          tags: <dockerhubusername>/mod:${{ steps.meta.outputs.tags }}
          build-args: |
            USER_ID=1000
            GROUP_ID=1000

crazy-max closed this as completed Oct 5, 2020

lskatz added a commit to lskatz/SneakerNet that referenced this issue Oct 5, 2020

updated the tag

b47014c

docker/build-push-action#160

JanWichelmann added a commit to JanWichelmann/ctf4e that referenced this issue Oct 7, 2020

Fix docker build action

f0b61f2

See docker/build-push-action#160

rfizzle added a commit to rfizzle/log-collector that referenced this issue Oct 21, 2020

fix: fixed docker build push context bug docker/build-push-action#160

edac0a7

haraldkubota added a commit to haraldkubota/hackathon-starter that referenced this issue Jul 19, 2021

Add context according to docker/build-push-action#160

22f6851

tonvanbart pushed a commit to Axual/ksml that referenced this issue Jun 3, 2022

try fix from docker/build-push-action#160

e8f0184

oppara added a commit to oppara/go-cve-dictionary that referenced this issue Jun 21, 2022

fix: insufficient_scope: authorization failed

328c84e

docker/build-push-action#160

oppara added a commit to oppara/go-cve-dictionary that referenced this issue Jun 22, 2022

fix: insufficient_scope: authorization failed

c6ff953

docker/build-push-action#160

jwokaty mentioned this issue Aug 10, 2022

Build and push Docker image not working waldronbios2/cunybios2#1

Open

jwokaty added a commit to jwokaty/cunybios2 that referenced this issue Aug 15, 2022

Fix tags

7079cd8

Recommended by docker/build-push-action#160

jwokaty mentioned this issue Aug 15, 2022

Fix tags waldronbios2/cunybios2#12

Merged

lam-man mentioned this issue Sep 17, 2022

docs(development_guide/READEME.md): add notes on missing configurations openservicemesh/osm#5132

Closed

This comment was marked as off-topic.

Sign in to view

m1sk9 mentioned this issue Feb 5, 2023

リリース時 ghcr.io へのイメージプッシュに失敗する approvers/OreOreBot2#701

Closed

2 tasks

agentbellnorm mentioned this issue Apr 3, 2023

Update release-tag.yml backstage/techdocs-container#49

Merged

TylerHelmuth mentioned this issue Apr 19, 2023

Release v0.1.0-alpha open-telemetry/opentelemetry-go-instrumentation#66

Closed

1 task

jaronoff97 mentioned this issue May 9, 2023

Cannot push to open source repo using community user bot #864

Closed

Yucked mentioned this issue Oct 11, 2023

insufficient_scope: authorization failed #987

Closed

3 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

insufficient_scope: authorization failed #160

insufficient_scope: authorization failed #160

AntonioFalcaoJr commented Oct 5, 2020 •

edited

Loading

socheatsok78 commented Oct 5, 2020

crazy-max commented Oct 5, 2020

socheatsok78 commented Oct 5, 2020

AntonioFalcaoJr commented Oct 5, 2020 •

edited

Loading

crazy-max commented Oct 5, 2020

AntonioFalcaoJr commented Oct 5, 2020

crazy-max commented Oct 5, 2020 •

edited

Loading

AntonioFalcaoJr commented Oct 5, 2020 •

edited

Loading

chase-moskal commented Jun 29, 2021

pffont commented Mar 23, 2022

Drallas commented Apr 19, 2022

philipzimmermann commented May 9, 2022

lclarkg18 commented Jun 2, 2022

moofoo commented Oct 29, 2022

This comment was marked as off-topic.

ummae commented Feb 10, 2024 •

edited

Loading

insufficient_scope: authorization failed #160

insufficient_scope: authorization failed #160

Comments

AntonioFalcaoJr commented Oct 5, 2020 • edited Loading

Behaviour

Steps to reproduce this issue

Expected behaviour

Actual behaviour

Configuration

Command produced

Logs

socheatsok78 commented Oct 5, 2020

crazy-max commented Oct 5, 2020

socheatsok78 commented Oct 5, 2020

AntonioFalcaoJr commented Oct 5, 2020 • edited Loading

Applying suggestion

Command produced

Logs

crazy-max commented Oct 5, 2020

AntonioFalcaoJr commented Oct 5, 2020

crazy-max commented Oct 5, 2020 • edited Loading

AntonioFalcaoJr commented Oct 5, 2020 • edited Loading

chase-moskal commented Jun 29, 2021

pffont commented Mar 23, 2022

Drallas commented Apr 19, 2022

philipzimmermann commented May 9, 2022

lclarkg18 commented Jun 2, 2022

moofoo commented Oct 29, 2022

This comment was marked as off-topic.

ummae commented Feb 10, 2024 • edited Loading

AntonioFalcaoJr commented Oct 5, 2020 •

edited

Loading

AntonioFalcaoJr commented Oct 5, 2020 •

edited

Loading

crazy-max commented Oct 5, 2020 •

edited

Loading

AntonioFalcaoJr commented Oct 5, 2020 •

edited

Loading

ummae commented Feb 10, 2024 •

edited

Loading