docker run image status 一直是 up 4 minutes

DOCKER RUN IMAGE STATUS 一直是 UP 4 MINUTES HOW TO

$ docker run -d centos:latest sleep infinityĭ651c7a9e0ad centos:latest 'sleep infinity' 2 seconds ago Up 2 seconds nervous_visvesvarayaĪs indicated by cjsimon, the -t option allocates a 'pseudo-tty'. Although it does rely on doing strange things like using sleep as your primary command. This does not rely doing strange things like allocating a TTY in daemon mode. (Did you mean to get to a bash prompt inside the container? That's easy! docker run -it centos:latest) SolutionĪ simple way to keep a container alive in daemon mode indefinitely is to run sleep infinity as the container's command. This is somewhat strange (because the container isn't doing anything useful until you interact with it, perhaps with docker exec), but there are certain cases where it might make sense to do something like this. What you appear to be trying to do is to keep the container alive without a daemon process running inside the container. In this case, as long as the httpd daemon is running, the container will remain alive. Normally, when you run a container in daemon mode (with -d), the container is running some sort of daemon process (like httpd). In your case, the command ( /bin/bash, by default, on centos:latest) is exiting immediately (as bash does when it's not connected to a terminal and has nothing to run). The container will continue to run as long as the command continues to run. So this would work: docker run -d centos tail -f /dev/nullĪ docker ps would show the centos container still running.įrom there, you can attach to it or detach from it (or docker exec some commands).Ī Docker container runs a process (the 'command' or 'entrypoint') that keeps it alive. In this situation, you can add tail -f /dev/null to your command.īy doing this, even if your main command runs in the background, your container doesn’t stop because tail is keep running in the foreground.

The problem is that some application does not run in the foreground. Otherwise, it thinks that your applications stops and shutdown the container. Your container immediately stops unless the commands keep running in foreground.ĭocker requires your command to keep running in the foreground. However, there is a problem with -d option. Instead of running with docker run -i -t image your-command, using -d is recommended because you can run your container with just one command and you don’t need to detach terminal of container by hitting Ctrl + P + Q.

Had to do: docker run -entrypoint '/bin/sh' -it alpine/git Note that for alpine, Marinos An reports in the comments:ĭocker run -t -d alpine/git does not keep the process up. d ps -aĬONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESĤa50fd9e9189 centos '/bin/bash' 8 seconds ago Up 2 seconds wonderful_wright That was initially reported in kalyani-chaudhari's answer and detailed in jersey bean's answer. In that case, you don't need any additional command and this is enough: docker run -t -d centos More recent versions of docker authorize to run a container both in detached mode and in foreground mode ( -t, -i or -it) That means, when run in background ( -d), the shell exits immediately. Alternatively, create a PR to suggest updates.The centos dockerfile has a default command bash. Let us know what you think by creating an issue in the Docker Docs GitHub repository.

Help us improve this topic by providing your feedback.

DOCKER RUN IMAGE STATUS 一直是 UP 4 MINUTES HOW TO

In the next module, we’ll learn how to run a database in a container and connect it to our application. We also looked at naming our containers so they are more easily identifiable.

We also took a look at managing containers by starting, stopping, and, restarting them. In this module, we took a look at running containers, publishing ports, and running containers in detached mode. That’s better! We can now easily identify our container based on the name. Run the following command in your terminal: Let’s start our image and make sure it is running correctly. The docker run command requires one parameter which is the name of the image. To run an image inside a container, we use the docker run command. Now that we have an image, we can run that image and see if our application is running correctly.Ī container is a normal operating system process except that this process is isolated and has its own file system, its own networking, and its own isolated process tree separated from the host. We created our image using the command docker build. In the previous module, we created our sample application and then we created a Dockerfile that we used to build an image. Work through the steps to build a Java image in Build your Java image.

Docker run image status 一直是 up 4 minutes