Katherine Rose
opened 1 year ago
-
Docker image push does go through http. Please push it to OneDev's 6610 directly to see if it works (check this tutorial on how to enable insecure registry via http protocol). If yes, it should Caddy server limiting the max upload size.
-
Forget to mention that the max upload size specified in performance setting is not related to this.
-
Previous Value Current Value Open
Closed
-
Please reopen if there is more info
-
Sorry, I do have clarifications: this is not a docker push command that I'm running from outside the OneDev container - this is OneDev's Build Docker Image CICD step. As far as I'm aware the only control I have over where that pushes is the repository and tag it pushes to.
-
Just tested I am able to push a 5G image to OneDev's built-in registry server through Caddy frontend. So I think it is Cloudflare limiting the max uploaded size.
-
That doesn't make sense - disabling Cloudflare's proxy didn't solve the issue. I don't see how it could be the issue given that. I'll do some more testing to make sure. If it is the issue, is there a way to have the Build Docker Image step push to the OneDev instance directly instead of to the public-facing hostname? Would using the insecure registry setting allow that?
-
Image push should be using the server url specified in system setting; otherwise there will be inconsistent auth endpoints.
| Type |
Question
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
I am trying to build a docker image and publish it to the internal registry in OneDev, but I get "request entity too large" errors. I tried increasing the max size in Performance Settings, and then setting it to 0, and neither worked. I suspected Cloudflare briefly but disabling their proxy didn't seem to affect my issue. My instance is behind a Caddy reverse proxy, but Caddy by default has no max upload size. Additionally, it seems like a docker image push shouldn't need an HTTP request if it's being pushed from OneDev to itself (isn't this something that Docker can do locally?), and if it absolutely does perhaps upload chunking could be used.