Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Private registry push reports "blob upload unknown" in client even though data gets pushed correctly #2225
My setup is following:
Previously this set-up was working when I didn't use https, I have the loadbalancer expose the registry as http on port 5000 and I can use it with "localhost:5000" address (on each machine where loadbalancer runs) - in this scenario pushing and using the images works fine.
Now I'm trying to push image to registry through https endpoint:
However even though push fails, the image is actually uploaded correctly, I can get its status and use it by new containers:
I enabled debug on client docker, here is an exempt from relevant time interval:
As could be expected, registry server is not reporting any problems:
I suspect something is configured incorrectly in loadbalancer doing https termination, since going through localhost:5000 works well. There must be some specific interaction of client and server that happens only during push, but not in any other operation, such that loadbalancer's https serving causes problems.
referenced this issue
Oct 5, 2017
@AndreaGiardini I think I might be running into the same thing, but I'm not a nginx expert, would you mind posting your config? or at least the portion you added?
Here's what i've done:
I'm seeing a similar issue with a docker registry (nexus3) behind AWS CloudFront. I've set the X-Forwarded-Proto, but the push still comes back with "unknown blob". After some minutes worth of delay (and all components are already pushed), the command completes successfully.