Visual Studio Code WSL Backend on Windows

Hi,

On Windows 10 with WSL2 backend it can not be started C++ project due to a problem in stage of creating Docker Image. It ended wit the error. The logs is as follow. Rebuilding SDK won’t solve the problem. In Linux environment with VS Code, everything is OK.

[2021-03-17T00:41:26.518Z] [PID 1944] 
[+] Building 11.5s (4/4) FINISHED
 => [internal] load build definition from Dockerfile                                                                                                                              0.0s
 => => transferring dockerfile: 844B                                                                                                                                              0.0s
 => [internal] load .dockerignore                                                                                                                                                 0.0s
 => => transferring context: 2B                                                                                                                                                   0.0s
 => ERROR [internal] load metadata for docker.io/library/sha256:7b78906f1af477d375de0e7804475df9282fcd71d8243c79c9c8f7ade5417d50                                                 11.4s
 => [auth] library/sha256:pull token for registry-1.docker.io                                                                                                                     0.0s
------
 > [internal] load metadata for docker.io/library/sha256:7b78906f1af477d375de0e7804475df9282fcd71d8243c79c9c8f7ade5417d50:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_
scope: authorization failed
[2021-03-17T00:41:26.552Z] [PID 1944] [12665 ms] Command failed: docker build -f c:\Work\REPOs\toradex\hello\.devcontainer\Dockerfile -t vsc-hello-c726abf60eae7925f418342784ec07fc c:\Work\REPOs\toradex\hello\.devcontainer

Hi @valter.tx, thanks for the answer. Adding "features": { "buildkit": false } into Docker configuration solves the problem.

Can you right click on the docker icon in the system tray, go to settings and then “docker engine”.
Check that you have:

“features”: {
“buildkit”: false
}

configure, otherwise please add it (inside the most external pair of curly braces) and restart docker.
This should fix the issue