-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to build Dockerfile #4023
Comments
Which version of Docker do you use? And didn't you enable buildkit feature in Docker https://docs.docker.com/develop/develop-images/build_enhancements/ ? If yes, you should disable it. |
I'm using Docker Desktop v 3.33 (64133), I didn't enabled buildkit. |
I can confirm that disabling the experimental features and disabling buildkit helped me move forward. If it helps there's a related issue with a screenshot of my docker desktop settings docker/for-mac#5186 (comment) However, my issue is not resolved, in the sense that I am still unable to get it going. Here's a log of what happened, and it's a long one.
|
I got same issue here : blockscout Version : 5397b97 Logs :
|
In the first case of error code 137, this indicates the docker engine has insufficient memory and/or disk space. You can configure the amount of memory docker uses either in the Docker Desktop settings, or from the CLI. See the docs for more. For the second case, error code 1; that can indicate a missing file or directory. The fix that worked for me was to do
|
I am unable to build docker image using the command
docker build --file docker/Dockerfile .
I also tried withCOIN=DAI ETHEREUM_JSONRPC_VARIANT=ganache ETHEREUM_JSONRPC_HTTP_URL=http://host.docker.internal:2000 ETHEREUM_JSONRPC_WS_URL=ws://host.docker.internal:2000 make start
Environment
elixir -version
): Not applicable as i am building docker imageSteps to reproduce
cd
into the repo.docker build --file docker/Dockerfile .
Expected behaviour
It should build docker image.
Actual behaviour
I get the following error
I also tried with
The text was updated successfully, but these errors were encountered: