+1 the same issue here
+1 - I have the same issue
+1 happening consistently for me too.
Same issue here, we are relying on docker hub to build our images.
We really need to have a reliable service for that, this issue is hurting our business…
We found a workaround to address that issue: In fact, Docker Hub don’t like when you COPY or ADD files or folders in the root directory.
So, for any COPY stuff / you have, you will need to do something like this:
COPY stuff /stuff
RUN cp -r /stuff/* / && rm -r /stuff
Thanks, @ccarre, your solution works for me! It’s broken not just for COPY or ADD but in fact any interaction in the root directory. So if somewhere you have
RUN wget -q -O file.ext http://somewhere
then you’ll need to change that to
RUN wget -q -O /stuff/file.ext http://somewhere
Well spotted, let’s hope for a fix though 
any update? it’s been 2 weeks and this is literally killing us.
UPDATE: The root cause of this issue has been identified and a temporary fix was deployed to production last night (11pm PDT), which has prevented subsequent occurrences of this issue. The upcoming release of Docker engine 1.12.3 includes an update that we have strong reason to believe will address the root cause of this issue. The team continues to treat this as a top priority and we will be updating this thread as more information is available.
Thanks a lot 
UPDATE: Docker engine 1.12.3 includes an update which addressed the root cause of this build failure. After upgrading the Docker autobuild service to Docker engine 1.12.3, we believe the issue has been resolved as subsequent occurrences of these build failures are no longer occurring. We apologize for the inconvenience and are taking steps to prevent similar issues from occurring in the future.