𝘛𝘦𝘤𝘩 𝘚𝘰𝘭𝘶𝘵𝘪𝘰𝘯 𝘏𝘶𝘣

Recently, I attempted to set up a docker repository for a project on my personal machine and encountered some unusual errors persisting for a few weeks. While it wasn’t a top priority, and no one else in the company had encountered it before, I began to suspect it might be an issue specific to my local setup on my new laptop. Despite the challenge of finding dedicated time amid competing priorities, I decided to allocate some focused time to troubleshoot the problem.

I’m passing on my insights to YOU, so you don’t have to go through the same challenges.

Error:

failed to solve with frontend dockerfile.v0: failed to read dockerfile: failed to mount in-place: {bind C:\ProgramData\Docker\windowsfilter\8od5jgmsfr4lya76uqw7t81nn [rbind ro]}: invalid windows mount type: ‘bind’

To fix this, you need to set buildkit as false.

{
  "builder": {
    "gc": {
      "defaultKeepStorage": "20GB",
      "enabled": true
    }
  },
  "experimental": false,
  "features": {
    "buildkit": false
  }
}

Why do we need to set buildkit as false?

In the docs, it’s currently mentioned BuildKit is a feature only supported for building Linux containers : https://docs.docker.com/develop/develop-images/build_enhancements/