moby: COPY failed: stat /var/lib/docker/tmp/docker-builder918577595/...

Check .dockerignore

You probably trying to copy files that are in .dockerignore.

This happened to me when trying to run the docker file from a different directory.

I had the COPY failed: stat /var/lib/docker/tmp/docker-builder929708051/XXXX: no such file or directory and managed to resolve this by specifying the docker file.

Running docker build . -f docker/development/Dockerfile worked.

But running Running docker build docker/development/Dockerfile` caused this issue.

-f or --file to specify the name and location of the Dockerfile.

It found it strange at first because when i had the Dockerfile in the apps root directory it worked fine. This will help if you want to manage your environment docker files a little better.

Running docker build docker/development/Dockerfile will use docker/development/Dockerfile as its build-context; any file referenced from the Dockerfile will need to be inside that path. Whereas docker build . -f docker/development/Dockerfile uses . (first argument) as build context, and loads the Dockerfile from docker/development/Dockerfile as if it was located at the root of the build-context (.)

Always check .dockerignore. I got a project from a third party and it included ‘*’. No wonder i couldn’t copy anything from the context. Thanks @comm1x for pointing it out.

thanks to pointing out the context issue @AshtonHylton-awin and @thaJeztah – that was the answer for me. For those of you using docker-compose.yml this type of block will do the equivalent of the docker build commands referenced above:

        build:
            context: .
            dockerfile: ./postgres/Dockerfile

COPY only able copy it’s subfolder .

Same problem. The funniest moment - everything was fine few iterations before. Looks like it got broken after COPY . /some_internal_path [it was the last successful try during this container development] (built via docker-compose with changed context)

I don’t know how to reproduce it, to be frankly. It’s broken now and I cannot find a solution to get it back to work at all.

> Docker version 17.09.0-ce, build afdb6d4
> Linux * 4.10.0-35-generic #39-Ubuntu SMP Wed Sep 13 07:46:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Does the file MyAgSourceAPI/conf/php/testsql.php exist in the path where you’re starting the build from? If you think it’s a bug, can you provide the exact steps to reproduce? Keep in mind that we don’t have access to your build environment, so cannot reproduce the steps you’ve written so far (i.e., we don’t have access to your Dockerfile, or the files you’re using in your Dockerfile.

I had the same problem on CentOS 7. It seems it’s related to either filename or filename length.

I had the problem with the filename: node-v6.11.0-linux-x64.tar.xz It worked with the filename: node.tar.xz

It was the same file, I just renamed it.

This might help find the bug.

Following working for me perfectly. I faced this issue, I was not able to copy zeppelin [1GB] directory into docker conatiner. and getting issue “COPY failed: stat /var/lib/docker/tmp/docker-builder977188321/zeppelin-0.7.2-bin-all: no such file or directory”

I am using docker Version: 17.09.0-ce and resolved issue by following steps.
Step 1: copy zeppelin directory [which i want to copy into docker package]into directory contain "Dockfile" 
Step 2: edit Dockfile and add command [location where we want to copy]
ADD ./zeppelin-0.7.2-bin-all /usr/local/  
Step 3: go to directory which contain DockFile and run command [alternatives also available]
docker build .

Step 4:  docker image created Successfully with logs
Step 5/9 : ADD ./zeppelin-0.7.2-bin-all /usr/local/
 ---> 3691c902d9fe
Step 6/9 : WORKDIR $ZEPPELIN_HOME
 ---> 3adacfb024d8 ....
Successfully built b67b9ea09f02

Does MyAgSourceAPI/conf/php/testsql.php exists in you current dir? All resources must exist in docker build PATH, see below:

Usage: docker build [OPTIONS] PATH | URL | -

Reading through this issue, I don’t think there’s a bug at hand here, so I’ll go ahead and close.

If you do think there’s still a bug after reading through this issue, please open a new ticket with the exact steps to reproduce.

@ahmedbokhari7 if you set the context: in your compose-file, both should work; see https://docs.docker.com/compose/compose-file/#context

in your case, context should probably be set to context: ./src/

dockerignore is the fix!! thanks

@frostyandy2k 's answer solved the problem