Action fails at Docker pull step

[shaftoe]

Hello there, not sure it's a temporary problem affecting me alone or not, FYI a few hours ago my builds have started to fail with the following:

Pull down action image 'ghcr.io/vladopajic/go-test-coverage:v2.18.0'
  /usr/bin/docker pull ghcr.io/vladopajic/go-test-coverage:v2.18.0
  v2.18.0: Pulling from vladopajic/go-test-coverage
  manifest unknown
  Warning: Docker pull failed with exit code 1, back off 2.179 seconds before retry.
  /usr/bin/docker pull ghcr.io/vladopajic/go-test-coverage:v2.18.0
  v2.18.0: Pulling from vladopajic/go-test-coverage
  manifest unknown
  Warning: Docker pull failed with exit code 1, back off 3.185 seconds before retry.
  /usr/bin/docker pull ghcr.io/vladopajic/go-test-coverage:v2.18.0
  v2.18.0: Pulling from vladopajic/go-test-coverage
  manifest unknown
Error: Docker pull failed with exit code 1
Pull down action image 'ghcr.io/vladopajic/go-test-coverage:v2.18.0'
  /usr/bin/docker pull ghcr.io/vladopajic/go-test-coverage:v2.18.0
  v2.18.0: Pulling from vladopajic/go-test-coverage
  manifest unknown
  Warning: Docker pull failed with exit code 1, back off 2.179 seconds before retry.
  /usr/bin/docker pull ghcr.io/vladopajic/go-test-coverage:v2.18.0
  v2.18.0: Pulling from vladopajic/go-test-coverage
  manifest unknown
  Warning: Docker pull failed with exit code 1, back off 3.185 seconds before retry.
  /usr/bin/docker pull ghcr.io/vladopajic/go-test-coverage:v2.18.0
  v2.18.0: Pulling from vladopajic/go-test-coverage
  manifest unknown
Error: Docker pull failed with exit code 1

Other actions are working fine as usual so I wonder if there is something wrong with the Docker hosting for the image?
HTH

[vladopajic]

@shaftoe thanks for reporting.
cc: @josielsousa, @charlesbjnr, @dweebo

not really sure what was going on. v2.18.0 did pushed successfully to docker ci action proof here.
now i run the same job again, and docker pull is working for v2.18.0.

[vladopajic]

note should you ever get similar error consider these temporary measures:

• set uses to specific version, version should be some earlier release
  uses: vladopajic/go-test-coverage@v2.17.1

• use source based action
  uses: vladopajic/go-test-coverage/action/source@v2

[shaftoe]

@vladopajic thank you for the quick reply! Actually I just re-run a failed test and it completed as expected so most probably it was some kind of transient problem, sorry for the fuss.

PS really like the tool! using it for a (temporary private) repo and it works great

[vladopajic]

thanks man, i really appropriate your feedback and contribution.

please consider this a kind reminder to start the project if you haven’t already. the tool is still not widely recognized by the broader community, and giving it a star is an easy, cost-free way to help it gain more visibility.

happy coding 🌞

[shaftoe]

Done already. FYI I got it recommended by some generative AI (can't remember which) when I was exploring how to enforce coverage for a private project.

[ilia-rassadin-rn]

I've just faced this issue, pulling the latest

docker pull ghcr.io/vladopajic/go-test-coverage:v2.18.0
v2.18.0: Pulling from vladopajic/go-test-coverage
failed to copy: httpReadSeeker: failed open: content at https://ghcr.io/v2/vladopajic/go-test-coverage/manifests/sha256:c56c2a56fa3aaf5a327aca507f4e8813e0234851738dcf3caff39042c0355841 not found: not found

As you might see, https://github.com/vladopajic/go-test-coverage/pkgs/container/go-test-coverage/565982430?tag=v2.17.1 here manifest file is present and here https://github.com/vladopajic/go-test-coverage/pkgs/container/go-test-coverage/581952837?tag=v2.18.0 it is missing.
Though we can see different OS/arch images for different architechtures. Looks like something is different for v.2.18.0 image

[taniabogatsch]

We're seeing the same in the duckdb-go project: https://github.com/duckdb/duckdb-go/actions/runs/19628872436/job/56203804184

      - name: Check Test Coverage
        uses: vladopajic/go-test-coverage@v2
        with:
          config: ./.github/testcoverage.yml

EDIT: reverting to older version as suggested above works (uses: vladopajic/go-test-coverage@v2.17.1).

[vladopajic]

reopening this issue as it has happened again and in case if it happens again people can see it and get to solution right away.