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!

    Corrupted docker images: error pulling image configuration: unknown blob

    Scheduled Pinned Locked Moved Support
    proget
    3 Posts 2 Posters 520 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

      We're using ProGet 4.7.11 and have started to notice that often after we publish a new revision of a docker image to proget's repository, that previous versions of the image are corrupted and cannot be used anymore. The error from docker is:

      error pulling image configuration: unknown blob

      There is no workaround but to update our code to use the latest revision of the image. We're using the default package store and disk path. I believe we saw this error in a previous version of Proget, 4.7.6, but we're seeing it a lot more as we are producing more and more revisions of an image in docker.

      Seen with docker mac client as well as docker in our ec2 instance. That's actually where we notice it: we're using ECS with Jenkins and the jenkins build hangs as it tries to start an older image (i.e. not latest) and can't because proget returns the "unknown blob" error.

      Here is example output from docker pull:

      je185066@WUSJE185066-RNZ ~/repos/silver/tf/tf-aws-iam$ docker pull proget.ncrsmb.com:443/docker-images/library/jenkins-slave-momentum:0.1.0.13

      0.1.0.13: Pulling from docker-images/library/jenkins-slave-momentum
      693502eb7dfb: Already exists
      081cd4bfd521: Already exists
      5d2dc01312f3: Already exists
      d685db7bb711: Already exists
      07ab343af037: Already exists
      9b3c1db2c50a: Already exists
      8dcb396c94a8: Already exists
      b803c12278f8: Already exists
      c0ef1b657d95: Already exists
      7385b6688cad: Already exists
      39d49faa9c96: Already exists
      b594c96ebcbb: Already exists
      6a822db54e6b: Already exists
      6a68823b4955: Already exists
      fecb56cad9b2: Already exists
      08236d8d14e0: Already exists
      0587696a1548: Extracting [==================================================>] 4.066 kB/4.066 kB
      41ee091ddf18: Pulling fs layer
      571f60c60d3c: Pulling fs layer
      error pulling image configuration: unknown blob

      Product: ProGet
      Version: 4.7.11

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        We are currently investigating this in a ticket from another user, and will try to update this when we have more information

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

          Hello Jeff,

          There is currently a bug in the FeedCleanup task for Docker feeds. PG-1030 has been fixed for the next version of ProGet, but until then, disable the FeedCleanup task for any Docker feeds in /administration/scheduled-tasks.

          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