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!

Error pulling image after upgrade proget:unknown blob



  • We're using ProGet 5.2.7.
    I build a windows container with following Dockerfile

    FROM mcr.microsoft.com/dotnet/framework/aspnet:4.7.2-windowsservercore-ltsc2019
    ARG source
    WORKDIR /inetpub/wwwroot
    COPY ${source:-obj/Docker/publish} .
    

    Because 4.3.1 not support windows container,so we upgrade our proget to latest version '5.2.7',after upgrade proget,docker push works fine,but docker pull on our kubernetes cluster occur an error 'unknown blob'.

    docker logs :

    Failed to pull image "testproget.schoolpal.cn/docker/library/clouderpapi:latest": rpc error: code = Unknown desc = unknown blob
    

    Product: ProGet
    Version:5.2.7



  • It seems all images can't pull successfully.
    When I trying pull Linux image which pushed before migration with following instrument:

    docker pull myproget/docker/library/disconf:20190702135059
    

    It shows following error:

    20190702135059: Pulling from docker/library/disconf                                                                                                                                                                                                                             [DEPRECATION NOTICE] registry v2 schema1 support will be removed in an upcoming release. Please contact admins of the myproget registry NOW to avoid future disruption.
    fc7181108d40: Downloading
    8b01d789a397: Waiting
    88b297f96aab: Waiting
    f523c3817e30: Waiting
    51f072905386: Waiting
    401f260c5b38: Waiting
    2f377f985fef: Waiting
    unknown blob                                                             
    

  • inedo-engineer

    Hello @yafeng-wu_3838

    I checked the second image and your ProGet instance definitely has all the layers for that image available as blobs.

    However, I noticed that the manifest was version 1, and version 2 of the manifest format was added with Docker v1.10.0 (released in 2016). Is the Docker client running on that machine very old? I'm wondering if this is related to the Content-Type header ProGet is sending causing the client to be confused.



  • @ben said in Error pulling image after upgrade proget:unknown blob:

    This is my docker client version

    Docker version 19.03.1, build f660560464
    

    OS Version :

    windows 2019 datacenter



  • If I create a new registry,everything is ok.
    but exists registry is not available


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation