gcrane: images in gcr.io/go-containerregistry/gcrane have errors and become unusable

### Describe the bug

The images in gcr.io/go-containerregistry/gcrane were updated yesterday and are not usable as before now

### To Reproduce

docker pull gcr.io/go-containerregistry/gcrane@sha256:f5439b41bf9909ecb413b40ebb10a9f4884bd0c82e61e415a5bcb588133e4936
gcr.io/go-containerregistry/gcrane@sha256:f5439b41bf9909ecb413b40ebb10a9f4884bd0c82e61e415a5bcb588133e4936: Pulling from go-containerregistry/gcrane
c98c7b4b8e5c: Extracting [==================================================>] 19.31kB/19.31kB
failed to register layer: Error processing tar file(exit status 1): archive/tar: invalid tar header

### Expected behavior

Should be able to successfully pull the image

### Additional context

Even though I was able to pull it with certain digest, e.g. docker pull gcr.io/go-containerregistry/gcrane@sha256:b04595f709812091b9f55059bce5bf05ef6c9869b677753b7c817167a0105368, running the command got `exec /ko-app/gcrane: exec format error`

Start by reproducing the failed docker pull for digest sha256:f5439b41bf9909ecb413b40ebb10a9f4884bd0c82e61e415a5bcb588133e4936 and the exec-format failure for the alternate digest. Compare the image behavior and publishing inputs, then verify that the gcrane image pulls successfully and runs without either error.

Written by the indexing model from the issue text.