Pulling from dotnet/core/sdk no matching manifest for windows/amd64 10.0.14393 in the manifest list entries

Bhoite, Vinod SBOBNG-PTIY/BE 6 Reputation points
2021-10-06T12:17:16.513+00:00

Getting below error while creating docker image of dotnet core 3.1 application on windows server 2016
Docker Command is:

docker build -t xxx .

Step 4/14 : FROM mcr.microsoft.com/dotnet/core/sdk:3.1 AS build-env
3.1: Pulling from dotnet/core/sdk
no matching manifest for windows/amd64 10.0.14393 in the manifest list entries

I googled and found one solution that, we need to set true to "Experimental" in docker desktop
but we can not install docker desktop on Windows Server 2016. So this solution is not for issue on windows server 2016.

Application Info: .net Core 3.1
Executing Docker command on OS: Windows Server 2016

I got below stackoverflow link where they mentioned
IS THIS TRUE?: "There are not any supported .NET Core images available for Windows Server 2016."

https://stackoverflow.com/questions/57912243/no-matching-manifest-for-windows-amd64-server-2016

Is anyone came across such issue and found solution, please share here.

Comments and suggestions are always welcome.

Developer technologies | ASP.NET | ASP.NET Core
Windows for business | Windows Server | User experience | Other
Developer technologies | .NET | Other
0 comments No comments
{count} vote

2 answers

Sort by: Most helpful
  1. Limitless Technology 39,926 Reputation points
    2021-10-06T19:14:54.11+00:00

    Hello @Bhoite, Vinod SBOBNG-PTIY/BE

    I have seen this error in the past due to a difference on the containers context Windows vs Linux. I would suggest verifying the next:

    RightClick Docker Icon in System Tray
    Click "Switch to Window" or "Linux Container" depending on which one you had selected previously.
    It may take little time
    Make Sure Docker is Running State Now and try again.

    Other option would be to run Docker on experimental mode to bypass some errors:

    Right click Docker icon in the Windows System Tray
    Go to Settings > Daemon > Advanced
    Set the "experimental": true
    Restart Docker

    If this doesn't work, I would recommend posting your issue in Docker forums, as their community they may be better equiped in experience with that errors within their software execution.

    Hope this helps with your query,

    ------------

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments

  2. Nilesh Warude 0 Reputation points
    2024-03-02T03:38:53.9033333+00:00

    User's image

    facing above issue ,already set experimental as true, can any one suggest any answer

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.