steam-deploy icon indicating copy to clipboard operation
steam-deploy copied to clipboard

Docker: Pull access denied, repository does not exist or may require 'docker login'

Open fajar-algorocks opened this issue 1 year ago • 3 comments

Bug description

Unable to find image 'ec5079:5098b2a473f5478699c0bf0ea7fa5c49' locally docker: Error response from daemon: pull access denied for ec5079, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.

How to reproduce

I'm not sure. I followed the instructions exactly. The build action succeeds on its own, but when I add steam-deploy, it fails.

Expected behavior

The process should work as expected without errors.

Additional details

Run game-ci/steam-deploy@v3
  with:
    username: ***
    configVdf: ***
    appId: ***
    buildDescription: v
    rootPath: Builds/StandaloneWindows64
    depot1Path: StandaloneWindows64
    depot1InstallScriptPath: StandaloneWindows64/install_script.vdf
    releaseBranch: internal-dev
/usr/bin/docker run --name ec50795098b2a473f5478699c0bf0ea7fa5c49_b274db --label ec5079 --workdir /github/workspace --rm -e "INPUT_USERNAME" -e "INPUT_CONFIGVDF" -e "INPUT_APPID" -e "INPUT_BUILDDESCRIPTION" -e "INPUT_ROOTPATH" -e "INPUT_DEPOT1PATH" -e "INPUT_DEPOT1INSTALLSCRIPTPATH" -e "INPUT_RELEASEBRANCH" -e "INPUT_TOTP" -e "INPUT_FIRSTDEPOTIDOVERRIDE" -e "INPUT_DEPOT2PATH" -e "INPUT_DEPOT2INSTALLSCRIPTPATH" -e "INPUT_DEPOT3PATH" -e "INPUT_DEPOT3INSTALLSCRIPTPATH" -e "INPUT_DEPOT4PATH" -e "INPUT_DEPOT4INSTALLSCRIPTPATH" -e "INPUT_DEPOT5PATH" -e "INPUT_DEPOT5INSTALLSCRIPTPATH" -e "INPUT_DEPOT6PATH" -e "INPUT_DEPOT6INSTALLSCRIPTPATH" -e "INPUT_DEPOT7PATH" -e "INPUT_DEPOT7INSTALLSCRIPTPATH" -e "INPUT_DEPOT8PATH" -e "INPUT_DEPOT8INSTALLSCRIPTPATH" -e "INPUT_DEPOT9PATH" -e "INPUT_DEPOT9INSTALLSCRIPTPATH" -e "steam_username" -e "steam_totp" -e "configVdf" -e "appId" -e "firstDepotIdOverride" -e "buildDescription" -e "rootPath" -e "depot1Path" -e "depot1InstallScriptPath" -e "depot2Path" -e "depot2Insta
Unable to find image 'ec5079:5098b2a473f5478699c0bf0ea7fa5c49' locally
docker: Error response from daemon: pull access denied for ec5079, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.
name: Build Development

on:
  workflow_dispatch:
  push:
    branches:
      - main
  pull_request:
    branches:
      - main

jobs:
  buildForSteam:
    name: Build [DEVELOPMENT]
    runs-on: ubuntu-latest
    outputs:
      buildVersion: ${{ steps.buildStep.outputs.buildVersion }}
    steps:
      # Checkout
      - name: Checkout repository
        uses: actions/checkout@v4

      # Cache
      - uses: actions/cache@v4
        with:
          path: Library
          key: Library-${{ hashFiles('Assets/**', 'Packages/**', 'ProjectSettings/**') }}
          restore-keys: |
            Library-

      # Build StandaloneWindows64 Steam DEV
      - name: Build StandaloneWindows64 DEV
        uses: game-ci/unity-builder@v4
        env:
          UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
          UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
          UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
        with:
          targetPlatform: StandaloneWindows64
          buildName: "AwesomeGame"
          buildsPath: 'Builds'
          customParameters: '-Development'

      # Direct Steam Deployment
      - name: Deploy to Steam
        uses: game-ci/steam-deploy@v3
        with:
          username: ${{ secrets.STEAM_USERNAME }}
          configVdf: ${{ secrets.STEAM_CONFIG_VDF }}
          appId: ${{ secrets.STEAM_APP_ID }}
          buildDescription: v${{ steps.buildStep.outputs.buildVersion }}
          rootPath: Builds/StandaloneWindows64
          depot1Path: StandaloneWindows64
          depot1InstallScriptPath: StandaloneWindows64/install_script.vdf
          releaseBranch: internal-dev

fajar-algorocks avatar Nov 20 '24 04:11 fajar-algorocks

The log is incomplete, the long line isn't showing which image it's trying to build, so I can't manually try to pull the image.

Are you running this on self-hosted or GitHub hosted runners? In case of self-hosted, you may need to add docker credentials as the error suggests. In case of GitHub hosted, I'd expect many people to have this same problem and some thumbs to this issue very soon.

Also, does this issue happen every time or was it just a flaky API call to Dockerhub?

webbertakken avatar Nov 20 '24 11:11 webbertakken

It turns out I have to separate the build and deploy jobs, and then both the build and deploy succeed.

However, I still prefer not to use artifact upload if possible.

Edit: This is using GitHub-hosted runners.

I tried combining the jobs again, but it failed just like before.

fajar-algorocks avatar Nov 21 '24 00:11 fajar-algorocks

I am having the same issue. Also, on my machine:

docker pull steamcmd/steamcmd:ubuntu-22
ubuntu-22: Pulling from steamcmd/steamcmd
89dc6ea4eae2: Downloading [=================>                                 ]  10.14MB/29.53MB
4f4fb700ef54: Download complete
e829285edaf9: Verifying Checksum
a8d5b55e9570: Verifying Checksum
a281e2b55a62: Verifying Checksum
7c929ec7edf1: Verifying Checksum
c9b3f359df99: Waiting
14823c36852d: Waiting
error pulling image configuration: image config verification failed for digest sha256:441c5ffd502b34568c64f48146f0825483bb6883be955863315a031045c347bd

skhaz avatar Jun 04 '25 12:06 skhaz