Menu
To enable BuildKit builds Easiest way from a fresh install of docker is to set the DOCKER_BUILDKIT=1 environment variable when invoking the docker build command, such as: $ DOCKER_BUILDKIT=1 docker build .
Docker Buildx is a CLI plugin that extends the docker command with the full support of the features provided by Moby BuildKit builder toolkit. It provides the same user experience as docker build with many new features like creating scoped builder instances and building against multiple nodes concurrently.
You must adjust the Docker Engine's daemon settings, stored in the daemon. json , and restart the engine. As @Zeitounator suggests, you should be able to temporarily disable the buildkit with DOCKER_BUILDKIT=0 docker build . .
I had experienced this issue after upgrading to the latest docker desktop version on mac. Solved with the comment on this issue
Solution: Don't use buildkit and it works for me.
export DOCKER_BUILDKIT=0
export COMPOSE_DOCKER_CLI_BUILD=0
I had the same issue and all I had to do was to capitalize the docker configuration filename
dockerfile > didn't work
Dockerfile > did work
Probably not the problem op had, but I had this issue while trying to build my container running inside Windows Subsystem for Linux (WSL) [Debian WSL2], just after having freshly installed docker-compose and all I had to do was close the [Debian] terminal and reopen it and my issue was solved.
If you are seeing this issue it is not actually the real issue. The actual issue is nested in the error logs somewhere. To see the actual issue you need to run your build command like this:
DOCKER_BUILDKIT=0 docker build .
Notice the DOCKER_BUILDKIT=0. That will make the build kit not hide the nested error. From there you should be able to google the correct solution.
This will also make the build look different in command line, but don't worry about that just look for the error.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With