"Bad range" error when pushing images to the container registry

[jacopo-j]

Description

I set up a simple Gitea Actions workflow for building a Docker image and publishing it on the container registry of the same Gitea instance. You can find the workflow file here.

During the publishing phase, the workflow fails with the following error:

::error::buildx failed with: ERROR: bad range format: 0--1

You can find the whole workflow log here, the error is at line 530-535.

I could not find any specific information regarding that error message, neither here nor elsewhere online. However, it likely comes from a response from the Gitea container registry.

By changing the workflow to publish the image con docker.io rather than my Gitea instance, everything works without errors, suggesting that the issue is not with a malformed Docker image (which I tried to re-build multiple times, by the way), but with the container registry itself.

Gitea Version

1.24.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.30.1

Operating System

macOS 11.6.3

How are you running Gitea?

Native using pre-build binaries for macOS

Database

MySQL/MariaDB

[wxiaoguang]

Are you able to build your own binary? If yes, could you try this fix? Fix container range bug #34725

[jacopo-j]

I tested the PR, and there is now a different error:

#13 ERROR: EOF
------
 > pushing my-gitea-instance.com/jacopo/my-repository:master with docker:
------
ERROR: EOF
::error::buildx failed with: ERROR: EOF

[wxiaoguang]

It looks strange, #34725 only fixes the wrong Range headers which didn't follow the spec, no idea why "EOF" now, or whether the EOF is related.

Is it possible to provide some reproducible steps with public images & docker cli?

[wxiaoguang]

By the way, I force-pushed a few times in #34725 (because at the beginning I have some misunderstanding and some old commits were wrong). The latest commit is dd53278 , is the EOF error caused by the latest commit when applied to the main or 1.24 branch?

[jacopo-j]

Sorry, you are right. The "EOF" issue was unrelated. I can confirm that your PR solves the issue.