Second push fails with ` requested access to the resource is denied` about docker-build-push HOT 9 CLOSED

Hi @adamgins - thanks for the feedback here. Happy to look into this deeper. Can you provide some details about what your Dockerfile looks like or even just the base image so I can reproduce?

from docker-build-push.

Using a simple "hello world" Dockerfile I'm not able to replicate this yet:

FROM mcr.microsoft.com/windows/servercore:ltsc2019

RUN dism.exe /online /enable-feature /all /featurename:iis-webserver /NoRestart

RUN echo "Hello World - Dockerfile" > c:\inetpub\wwwroot\index.html

CMD [ "cmd" ]

According to this StackOverflow issue, your issue may be related to the docker login operation.

from docker-build-push.

Thanks @mr-smithers-excellent
I added you to a private repo we run the docker file in the bundle directory
Weird that is succeeds with the push the first time to a new docker image and then fails the second time.

from docker-build-push.

@mr-smithers-excellent FYI I did find this long issue docker/hub-feedback#1222

from docker-build-push.

@adamgins - this is helpful. Looking into this more today.

from docker-build-push.

@adamgins - think I found your issue.

Successful Build Image
buzzybuzz/buzzy-main-windows-nano1809:latest

Failed Build Image
buzzybuzz/buzzy-main-windows:nano1809

I'm guessing the name of the Docker repo should be buzzy-main-windows-nano1809? Does the repo buzzybuzz/buzzy-main-windows exist?

from docker-build-push.

@mr-smithers-excellent thanks. I think that issue was just an example where we changed the image name to a new name buzzybuzz/buzzy-main-windows-nano1809:latest and it worked the first time. Both those images existed on docker.io

The weird thing is I got it to work on buzzybuzz/buzzy-main-windows by deleting the repo and then re-running, it worked both first and second time.

The only other things I changed, was I added the latest as the tag directive:

build:

    runs-on: windows-2019

    steps:
      - uses: actions/checkout@v1
        name: Check out code
    # - uses: actions/checkout@v2
    # - name: Build image from archive
    #   run: docker build --build-arg s3key=${{ secrets.AWS_ID }} --build-arg s3scret=${{ secrets.AWS_SECRET }} --build-arg s3path=s3://<path to s3bucket>/<file>.tar.gz -t buzzybuzz:buzz-main-windows -f bundle/Dockerfile .
    # - name: Run build-tools build command
      - uses: mr-smithers-excellent/docker-build-push@v3
        name: Build & push Docker image
        with:
          image: buzzybuzz/buzzy-main-windows
          tag: latest
          registry: docker.io
          dockerfile: bundle/Dockerfile
          username: ${{ secrets.DOCKER_USER }}
          password: ${{ secrets.DOCKER_PASSWORD }}
          buildArgs: s3key=${{ secrets.AWS_ID }}, s3scret=${{ secrets.AWS_SECRET }}, s3path=s3:/<path to docker bundle>/<file>.tar.gz

So I'd say it's working, I still don't know what made it work. The critical thing was deleting the current image.

from docker-build-push.

Let me know if the issue creeps up again. I'll be on the lookout for similar problems. Closing this for now. Thanks!

from docker-build-push.

Thanks @mr-smithers-excellent

from docker-build-push.