The result is that you get an interactive terminal and the container keeps running. Now, the bin/bash/ command can accept input and docker run -it IMAGE_ID command attaches STDIN to the container. When you build a image and not specify any command with CMD or ENTRYPOINT, the base image's CMD or ENTRYPOINT command would be executed.įor example, the Official Ubuntu Dockerfile has CMD ( ). From the Dockerfile reference,īoth CMD and ENTRYPOINT instructions define what command gets executed whenĭockerfile should specify at least one of CMD or ENTRYPOINT commands.

Generally, when a docker container is run, an application is served by running a command. Here's a solution when the docker container exits normally and you can edit the Dockerfile. The answer is CMD in a dockerfile or command in the following expression, which is bash by default in some images, i.e. When does the process exit? In another word, what’s the process, how did we start it? When the process exits, theĬontainer holding process would exit too. Coming the most important one, a container actually imagine itself.Thus container would be in Stopped status. When docker stop, obviously docker daemon will stop a container.When we execute docker run, docker daemon will finish it in two.Which its status may be Created or Stopped. When docker start, docker daemon will start a existing container.When we execute docker create, docker daemon will create a.The status of a container includes Created, Running, Stopped,.I add some extra information, which may provide a further understanding about this issue. The reason is just what the accepted answer said.

Time is running out image