Docker build state
FROM someImage MAINTAINER abc ENV something=somehow RUN sh calculatePi.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.
- Is this dockerfile even plausible?
- 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?
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
calculatePi.sh 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 MAINTAINER abc ENV something=somehow ENV somethingElse=somehow2 ENTRYPOINT ["/bin/bash"] CMD ["calculatePi.sh"]
Then when you run this image
docker run -d thisImage
The script calculatePi.sh will run in your container as an App.