'docker build' gives error that 'docker run' doesn't. How are they different?

My project is setup like this:

./ -
    compiled files from frontend and backend directories get put here
    frontend files...


  • Docker development workflow for compiled components in a docker-compose setup
  • How to rebuild go project efficiently while using Docker Compose?
  • Build Docker in VM
  • How to build a Docker image for an Arm architecture on a Mac?
  • Dockerizing Jenkins builds - slaves as containers or builds as containers?
  • Nginx proxy, linked to other docker containers
  • docker build ../ --tag myImage
    # The build script compiles all my assets and places 
    #  them in the top level 'build' directory which i am 
    #  trying to link to my docker image so I can recompile 
    #  on each file change and have the changes show in the docker image.
    docker run --volume /path/to/build/dir:/src/app myImage


    FROM node:4.4.7
    RUN ls src/app

    The RUN command in the Dockerfile gives me this error when the build command from the startServer script is called:

    ls: cannot access src/app: No such file or directory

    If I change RUN to CMD it gives no error. Also, even after the build gives that error, it finishes the build and the docker run command gives no error.

    1. Is the ‘docker build’ command actually trying to add the ‘build’ folder to the image from which containers are launched? Or is it just compiling some commands for the images to use when they are made?

    2. If it is the later, how do you make one Dockerfile that is used for both building and running that works in both cases?

    I feel like I might be missing a crucial concept with Docker, but I’ve gone through the tutorials and docs and couldn’t solve this.

  • Running Mkbootstrap for DBI () => DBIXS.h:22:20: fatal error: EXTERN.h: No such file or directory
  • Docker doesn't open ports
  • Redis: ERR Rewriting config file: Permission denied when using Docker data volume
  • Docker - What is proper way to rebuild and push updated image to docker cloud?
  • file system issue when i use vagrant+docker on windows
  • Wordpress Docker won't increase upload limit
  • 2 Solutions collect form web for “'docker build' gives error that 'docker run' doesn't. How are they different?”

    There is no src/app folder in the node image, so this is an expected error. The node image expects you to add your own /usr/src/app, either with a COPY step in your build, or with a volume mapping after the build is finished.

    The RUN gives a step to run to add a layer to the resulting built image, so an ls makes little sense there since you didn’t modify the image with new content.

    The CMD gives a default command to run if one is not passed at the end of the docker run, so if you do a docker run node /bin/bash, the ls src/app CMD will never be run. This also runs after other steps in your build, and after any volume mounts you may be running on your container, which would create this folder.

    When you run the docker image, you mount data volume to /src/app

    But in docker script, you tried to access src/app
    Because the default working directory is not a root. you cannot access src directory.

    so, edit your docker file to

    FROM node:4.4.7
    RUN ls /src/app
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.