Brandon Mitchell

Hi @smokhov, getting a 404 on the upload is curious. Include the previous 10 or so lines of logs in case they give more detail. Perhaps the ~30 minutes has...

Oops, I guessed wrong on the number in the brackets, couldn't remember if that was seconds or minutes. You're right, ~30 seconds shouldn't be hitting any session timeouts. Seeing those...

The "sleeping for backoff" line indicates the previous request failed in a way that can be retried. Likely a network drop. So the successes indicate that the request made it...

I've made some changes to the error handling of the patch responses to deal with the known responses. Hopefully Docker is following their own spec there because the behavior is...

@smokhov > I've pulled the new binary, it does about the same That means the 404 isn't including a new upload location and range header. Not entirely surprising since it's...

Here's the latest CI run with binaries that you can test: https://github.com/regclient/regclient/actions/runs/3223453135 The 404 is still concerning because it implies that Hub may have destroyed the UUID associated with the...

Just a follow up that this is being worked on by distribution/distribution which is the upstream project used by registries like Docker Hub. I have no idea how long it...

> BTW, just by waiting and doing nothing a couple of days later I was able to push. That sounds a lot like some kind of bandwidth throttling killing long...

It's currently undocumented while I get an environment too test it, since most registries reject an incomplete manifest list. That flag is `--platforms` (plural), e.g.: ```shell regctl image copy \...

Seeing this on a fresh lab deploy, no other containers running, CentOS 7, with userns enabled. My Debian 10 environment isn't seeing any issues. Disabling userns made the issue go...