Skip to content
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

Docker build stucks at "Sending build context to Docker daemon 556.1kb" #2388

Closed
JasonShin opened this issue Aug 1, 2017 · 5 comments
Closed

Comments

@JasonShin
Copy link

This bug-tracker is monitored by developers and other technical types. We like detail! So please use this form and tell us, concisely but precisely, what's up. Please fill out ALL THE FIELDS!

If you have a feature request, please post to the UserVoice. If you're reporting a BSOD, don't post here! Instead, e-mail "secure@microsoft.com", and if possible attach the minidump from "C:\Windows\minidump".

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    Microsoft Windows [Version 10.0.14393]

  • What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)
    ``` docker build -f .docker/client.dev.dockerfile . ````

  • What's wrong / what should be happening instead:
    It stucks at "Sending build context to Docker daemon 556.1kb" all the time.

  • Strace of the failing command, if applicable: (If <cmd> is failing, then run strace -o strace.txt -ff <cmd>, and post the strace.txt output here)
    Somehow when I try
    strace -o strace.txt -ff docker build -f .docker/client.dev.dockerfile .
    it starts to build correctly after spitting out "ERRO[0001] Can't add file /home/xxx/xxxx/xxxxx/trace.txt.311 to tar: archive/tar: write too long"

See our contributing instructions for assistance.

What is happening?

@sunilmut
Copy link
Member

sunilmut commented Aug 2, 2017

@JasonShin - Thanks for your post. This looks like #610, #616 et. al. Your are running Anniversary Update (build 14393). There have been significant improvements since and these issues should be fixed in Creators Update. Updating to that should resolve your issues. Let us know if it doesn't.

@sunilmut
Copy link
Member

I am closing this out. If this repro's for you in Creators Update, please comment and we can reopen.

@JasonShin
Copy link
Author

hey, how do I get creators update and how do you check if I am already on it?

@JasonShin
Copy link
Author

Cheers, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants