Docker build state

I have an existential question about docker. Given this dockerfile:

FROM someImage
ENV something=somehow
RUN sh
ENV somethingElse=somehow2

“Calculate Pi” is a “continuous” program that never ends and needs to be ran on the background. It calculates all the digits of PI (3.1415…..) and save it to a txt file.

  • I can not access my Container Docker Image by HTTP
  • Configure the network interfaces of the host a docker container is running on
  • How is it possible for two identical Docker images to have different packages installed?
  • Docker library/base not found?
  • Using Spinnaker to deploy a Docker image from dockerhub to Aws Eb
  • How to implement CPU & memory docker container restrictions on GCE + MYSQL backup/restore?
  • My question:

    1. Is this dockerfile even plausible?
    2. If Yes, When I run a container based on this image, what is the saved state? In other words, if I open the txt file, what would I see?

  • Tag a docker container?
  • Auto-provision new hosts with docker swarm
  • Create a new Docker VM
  • java.lang.RuntimeException: No main class detected
  • Difference between production and development docker using
  • docker-machine connect to existing machine
  • 3 Solutions collect form web for “Docker build state”

    When Docker builds an image, each instruction in the Dockerfile gets executed in an interim container, run from the preceding image layer. So if your ran endlessly then your image would never build – it would stick at the RUN instruction waiting for it to complete.

    In practice, it’s more likely that you’ll max out disk or CPU resource and take down the machine if you tried to build it. Either way, you wouldn’t get a completed image that you could run.

    No, that Dockerfile won’t work. RUN instructions need to complete before Docker can create an image from them. Perhaps you want to make that a CMD instruction instead?

    May be you can write your docker file like this:

    FROM someImage
    ENV something=somehow
    ENV somethingElse=somehow2
    ENTRYPOINT ["/bin/bash"]
    CMD [""]

    Then when you run this image

    docker run -d thisImage

    The script will run in your container as an App.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.