Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    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

    Scheduled Pinned Locked Moved Support
    proget
    2 Posts 2 Posters 55 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      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

      1 Reply Last reply Reply Quote 0
      • benB Offline
        ben inedo-engineer
        last edited by

        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.

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation