'docker build' error: "failed to solve with frontend dockerfile.v0"

[nromagno]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: DAA27533-4D93-4AF4-916C-8492CC6BF66B/20201015121621

Expected behavior

I expect to build a docker image from my Dockerfile for my R Shiny application.

Actual behavior

I get the resulting error from the docker build command:

Information

Docker version is:

Windows Version: Windows 10 Home, version 1909

And docker run hello-world does work as expected:

I'm working with Docker Desktop for Windows 10 Home and I've followed this guide for the installation:
Install Docker Desktop on Windows Home

Since I think I have followed the guide correctly, and passed the docker run hello-world test, I'm not sure how to begin debugging this error.

I would really appreciate any help on clarifying what the error means, and how to potentially address it. Thank you!

[stephen-turner]

Thanks for the report, moving to buildx repository.

[tonistiigi]

Please post docker version and a reproducer. Also, check if there is anything interesting in the daemon logs.

[nromagno]

@tonistiigi my docker version is:

Also, by reproducer, do you mean a reproducible example?

And for the daemon logs you suggested, I'm not sure if I have been able to locate them correctly. I followed the advice here on where to find them (on my Windows it was under AppData\Local\Docker and I found this log.txt file.

I looked through the log.txt file but I couldn't find anything helpful.

Is this the correct file? And did I miss something important within it?

[Muqito]

I noticed this as well with the same version after the update.

Fixed after I purged the settings and restarted.

[ArifIstaka]

Name the file Dockerfile exactly. I got the same error because i named it DockerFile

[UlasKasim]

changing name 'Dockerfile' from 'dockerfile' also worked for me

[nromagno]

@UlasKasim @ArifIstaka the name of the file is already capitalized.

@Muqito Can you clarify a little bit on how you "purged the settings and restarted." Thanks!

[Muqito]

@nromagno Sure thing.

Click on this little bug icon up to the right, and then you'll see the following settings:

I think I might have also reset to factory settings. Not sure though

[nromagno]

@Muqito I purged the data and restarted as you described, but unfortunately the same error still appears.

[Kusanagi-2029]

@stephen-turner, @tonistiigi, @nromagno, Good afternoon! I am new to Docker. I try to run the image and container based on it by reading the Microsoft documentation step by step:
https://docs.microsoft.com/ru-ru/dotnet/core/docker/build-container?tabs=windows
But if I specify a Dockerfile without an extension, then I encounter an error reading Dockerfile by Docker itself (for some reason, it does not see the Dockerfile in this directory). When I specify the .txt extension (docker build -t counter-image -f Dockerfile.txt .
), Docker sees this file:

So do I not understand something due to lack of experience, or is there really some problem?

 Best regards, Kusanagi-2029

[bravecobra]

I just hit the same issue. I use the WSL2 engine, which is of course case-sensitive. The command sent to docker from Visual Studio is specifying a fully lowercase path, which breaks the command of course.

[llwydsj]

I just hit the same issue. I use the WSL2 engine, which is of course case-sensitive. The command sent to docker from Visual Studio is specifying a fully lowercase path, which breaks the command of course.

Same here. Visual Studio debugging with Docker works fine. Output window shows:
>docker build -f "C:\dev\src\Project.Name\Dockerfile" args...
But building from the context menu when right clicking on the Dockerfile in the solution explorer executes this:
>docker build -f "c:\dev\src\project.name\dockerfile" args...

[bette]

This may help someone else:
The instructions say to make sure you are in the directory "node-bulletin-board/bulletin-board-app" and I was getting the above error when running in "node-bulletin-board". Changed into the bulletin-board-app child directory and it ran. Naturally I only re-read the doc after trying everything else.