Docker Community Forums

Share and learn in the Docker community.

[RESOLVED] ADD file in Dockerfile fails w/ ' stat: ... no such file or directory '


(Imjosh2) #1

Building on Dockercloud nodes. Sometimes it works, sometimes it doesn’t:

Starting to clone
Cloning into '.'...
Warning: Permanently added the RSA host key for IP address '' to the list of known hosts.
Switched to a new branch 'dev'
Cloning done
Getting README
Getting Dockerfile
KernelVersion: 4.4.0-34-generic
Os: linux
BuildTime: 2016-07-28T22:11:10.070091404+00:00
ApiVersion: 1.24
Version: 1.12.0
GitCommit: 8eab29e
Arch: amd64
GoVersion: go1.6.3
Starting build of
Step 1 : FROM node:4
---> e8428963b85a
Step 2 : ENV VIRTUAL_HOST pdf.localhost
---> Running in d07283d045d5
---> 6309785bdb1f
Removing intermediate container d07283d045d5
Step 3 : ADD /
Removing intermediate container efc856b05147
stat /var/lib/docker/overlay/dbf8d11e9c8c02070972a6b0c192469057a0394b7193eeb8ce804294b346dc5c/merged/ no such file or directory

(Viktor Shlapakov) #2

I’ve encountered with the same issue, as was stated - sometimes it works, sometimes doesn’t, please investigate:

Step 9 : COPY requirements.txt /stack-requirements.txt
Removing intermediate container 8860323d9fab
 stat /var/lib/docker/overlay/cb3ede47575411849fcec51f008fbe2b91928a0eefba200edbc350e2ea1b27d2/merged/stack-requirements.txt: no such file or directory
ERROR: Build failed: stat /var/lib/docker/overlay/cb3ede47575411849fcec51f008fbe2b91928a0eefba200edbc350e2ea1b27d2/merged/stack-requirements.txt: no such file or directory
ERROR: Build failed with exit code 2
ERROR: Build in 'branch-1.0' (89fab134) failed in 0:04:35

(Ryan Kennedy) #3

Thanks for the feedback. The team is aware of the issue and actively working on a fix.

(Ryan Kennedy) #4

UPDATE: The root cause of this issue has been identified and a temporary fix was deployed to production on Mon, 10/24 at 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.

(Ryan Kennedy) #5

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.

(Ryan Kennedy) #6