-
Notifications
You must be signed in to change notification settings - Fork 288
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
Stuck on "Sending build context to Docker daemon" #576
Comments
I just attempted to update to the latest version on docker on unix such that server and client matches.
This gives me the following:
|
I have found this thread which seems to document some of the same issues, but without a solution.
The docker client seems to use the v1.26 API which the docker-compose client uses the v1.21 client. Could this be a regression with a new API version? |
I think this is a known bug in WSL: microsoft/WSL#1123 (comment) Fwiw I can't repro on my latest insider build so it's possible that they fixed it:
|
In my case a co-worker advised to assign more runnable memory to Docker which helped. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
I have an container that should have a build context of 32 mb. When I run
docker build .
I expect the container to be built.Actual behavior
When I run
docker build .
it is stuck onSending build context to Docker daemon 1.114 MB
. I have tried with the same image(private image) on a different laptop, but under the same setup and the result is the same. I have trInformation
DOCKER_HOST=tcp://127.0.0.1:2375
.docker version
:Steps to reproduce the behavior
mkdir src
dd if=/dev/zero of=src/output.dat bs=32M count=1
docker build .
The text was updated successfully, but these errors were encountered: