Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Docker push fails
-
I'm trying to push to docker registry, but it fails with this message in the logs:
A 404 error occurred in docker: blob unknown to registry.
This is the stack trace
URL: http://companydomain.com:8080/v2/docker/dotnet/blobs/sha256:4fb899b4df216ab398fb05547f86dc371db944cf53dea7913d2f4261ed09e2be
Referrer: https://companydomain.com/v2/docker/dotnet/blobs/sha256:4fb899b4df216ab398fb05547f86dc371db944cf53dea7913d2f4261ed09e2be
User: docker
User Agent: docker/18.03.0-ce go/go1.9.4 git-commit/0520e24 kernel/4.9.87-linuxkit-aufs os/linux arch/amd64 UpstreamClient(Docker-Client/18.03.0-ce (windows))
Stack trace: at Inedo.ProGet.WebApplication.SimpleHandlers.Docker.DockerHandler.<ProcessBlobAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.WebApplication.SimpleHandlers.Docker.DockerHandler.<ProcessRequestAsync>d__5.MoveNext()Any idea why this is happening? Something to do with SSL termination happening on another server (apache reverse proxy)?
Cheers
Product: ProGet
Version: 5.0.10
-
Hello Lev,
A possible reason this might be happening is if Apache is caching the 404 error returned by Docker when the client checks for an existing layer and then returning the cached error after the layer is uploaded and the blob URL becomes valid.
