I am bit confused on the status of the docker container, especially with status as CREATED.
I know that when the container is running state it shows as below:
root#labadmin-VirtualBox:~/RAGHU/DOCKER# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1261afc2acc1 302fa07d8117 "/bin/bash" 43 minutes ago Up 43 minutes optimistic_thompson
And if the container is stopped, it shows as below:
root#labadmin-VirtualBox:~/RAGHU/DOCKER# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
935f902efac7 302fa07d8117 "/bin/bash" 44 minutes ago Exited (0) 44 minutes ago competent_golick
5eb1c2525e2e 302fa07d8117 "/bin/bash" 44 minutes ago Exited (0) 44 minutes ago friendly_saha
My confusion is in what state does the docker shows the status of the container as CREATED:
root#labadmin-VirtualBox:~/RAGHU/DOCKER# docker ps -a | grep -i created
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
01c63f92586b jenkins "/bin/tini -- /usr..." 5 weeks ago Created gloomy_jones
Docker status Created means that the container has been created from the image, but it has never been started.
This state can be achieved in this two ways.
Docker container has been created using docker create command (this is done to speed up container creation).
Docker container has been created using docker run but it hasn't been able to start successfully.
For further information check docker create reference: https://docs.docker.com/engine/reference/commandline/create/
Related
I have created a container locally. Then, I run the following command:
docker ps -a
output is:
ONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
abc6f4d50931 airflow "/bin/zsh" 17 hours ago Exited (137) 21 minutes ago xenodochial_mclaren
Then I try to run the container with the following command, it create a new container with same IMAGE but different container ID instead opening the container with this image name which exist.
docker run -p 8080:8080 -it airflow /bin/zsh/
The output of docker images command is:
REPOSITORY TAG IMAGE ID CREATED SIZE
airflow airflow 63e2e36735a6 46 hours ago 704MB
airflow latest 63e2e36735a6 46 hours ago 704MB
docker/getting-started latest 083d7564d904 6 weeks ago 28MB
Why is this creating new containers?
If you run docker run ... you spin out a new cointainer from the image.
The status of your container is Exited as you can check from the docker ps -a output.
If you want to start again the same container, you can try docker start abc6f4d50931.
I tried to start a container output as follows,
I have listed all available containers using docker ps --all.
[root#sdctlt0048 express_edition]# docker ps --all
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ceb4b5256c32 store/saplabs/hanaexpress:2.00.045.00.20200121.1 "/run_hana --passwor…" 6 hours ago Exited (1) 3 hours ago express_edition
7d838bf619df 389fef711851 "echo hello" 4 days ago Exited (0) 4 days ago helloWorld
b743cad7815f portainer/portainer-ce "/portainer" 2 weeks ago Up 2 weeks 0.0.0.0:8000->8000/tcp, 0.0.0.0:9000->9000/tcp portainer
47cc21a338dd portainer/portainer "/portainer" 2 weeks ago Exited (1) 2 weeks ago youthful_maxwell
97e277d42155 hello-world "/hello" 2 weeks ago Exited (0) 2 weeks ago confident_roentgen
I entered the following commands to start the container which is in the exit stage and enter the terminal of this image.
docker start ceb4b5256c32
docker exec -it ceb4b5256c32 bach
It throws the following error.
FATA [0000] Error response from daemon: Container ceb4b5256c32 is not running
But when I start the container using docker start ceb4b5256c32. It throws the container ID out, which is okay if everything is working normally. I am not sure what caused this error.
for my docker run i was created a script where I put all my commands as follows:
Any idea on the causes and suggestions on this would be very helpful to me.
many Thank in advance.
Mb the container has already stopped when you want to execute the command?
Check if conatainer have a status Exited and logs
docker ps | grep ceb4b5256c32
docker logs ceb4b5256c32 --tail 5
If the container always stops and this is normal then try it (--rm - remove container after stopped):
docker run --rm -it <image:name> <command>
Eg:
# ~ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
# ~ docker run --rm -it debian bash
root#22ce8b31b68c:/# exit
exit
# ~ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
# ~
Using an image from https://hub.docker.com/_/php.
Create and launch a hogehoge-php container with docker run -dti
% docker run -dti --name hogehoge-php php
Then I can see that the hogehoge-php container is up and running.
confirmed:
% docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2c9e7ff1a952 php "docker-php-entrypoi..." 6 seconds ago Up 5 seconds ago hogehoge-php
try with pull, create and start
I read that the docker run is a command that performs docker pull, docker create, and docker start all at once. So I decided to try it out as follows (I didn't do the docker pull because I already have a local php image).
% docker create --name foofoo-php php
c7687c088dda9b71d9380e9ca472afa436ac63785c1d2c195b8a08147f8adec9
% docker start foofoo-php
foofoo-php
% docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c7687c088dda php "docker-php-entrypoi..." 16 seconds ago Exited (0) 3 seconds ago foofoo-php
When I tried as above, I got Exited (0) 3 seconds ago, and the foofoo-php container created by docker create doesn't stand up all the time.
The foofoo-php container made by docker create doesn't stand up(options not available).
% docker start -dti foofoo-php
unknown shorthand flag: 'd' in -dti
See 'docker start --help'.
The i option is available, and I was able to run it, but it doesn't leave the docker running.
% docker start -i foofoo-php
Interactive shell
% docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c7687c088dda php "docker-php-entrypoi..." 3 minutes ago Exited (0) 5 seconds ago foofoo-php
How can I create and start instead of run -dti?
By the way, I tried docker run without -dti
By the way, I tried docker run without -dti.
% docker run --name barbarbar-php php
Interactive shell
% docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6215c71a13a4 php "docker-php-entrypoi..." 15 seconds ago Exited (0) 15 seconds ago barbar-php
The container was created, but it's not standing up. I thought I should try docker start:
% docker start barbar-php
barbar-php
% docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6215c71a13a4 php "docker-php-entrypoi…" 33 seconds ago Exited (0) 3 seconds ago barbar-php
but the container doesn't start up.
On the other hand, stop and start a container created by docker run -dti
On the other hand, try to stop and start a container created by docker run -dti, it running up after start.
% docker stop hogehoge-php
hogehoge-php
% docker start hogehoge-php
hogehoge-php
% docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6215c71a13a4 php "docker-php-entrypoi…" 4 minutes ago Exited (0) About a minute ago barbar-php
c7687c088dda php "docker-php-entrypoi…" 11 minutes ago Exited (0) 8 minutes ago foofoo-php
2c9e7ff1a952 php "docker-php-entrypoi…" 14 minutes ago Up 2 seconds hogehoge-php <----- Here
Behavior Summary
docker run
with dit option
up after a run
up after start
without dit option
not up after a run
not up after a start
docker create
not up after a run
What you are missing is a docker create -t to allocate a pseudo-TTY for you container.
Since the entrypoint for the image you are running is a php shell running at the foreground, the container, when started, figures out that it doesn't have a tty to attach to an exit with 0.
docker pull php
docker create -t --name hogehoge-php php
docker start hogehoge-php
Docker containers are deployed through gitlab-ci.yml. In repos we have docker file, Docker-compose.yml, .gitlab-CI.yaml. and some other files. So when run ajob. Container is getting created as expected but it is going to exited state after some time. What Should I do to make it up all the time
<Container ID> <imageID> "/bin/sh -c 'chown -…" 9 hours ago Exited (1) About an hour ago
On my remote server, some developers run the same docker images named "my_account/analysis". So, once detached from the docker process, it is struggling to know which is my own process.
The result of docker ps is like this:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6968e76b3746 my_account/analysis "bash" 44 hours ago Up 44 hours 6023/tcp, 6073/tcp, 6800/tcp, 8118/tcp, 8888/tcp, 9050/tcp, 0.0.0.0:8887->8887/tcp modest_jones
42d970206a29 my_account/analysis "bash" 7 days ago Up 7 days 6023/tcp, 6073/tcp, 6800/tcp, 8118/tcp, 8888/tcp, 9050/tcp, 0.0.0.0:32771->8885/tcp gallant_chandrasekhar
ac9f804b7fe0 my_account/analysis "bash" 11 days ago Up 11 days 6023/tcp, 6073/tcp, 6800/tcp, 8118/tcp, 8888/tcp, 9050/tcp, 0.0.0.0:8798->8798/tcp suspicious_mayer
e8e260aab4fb my_account/analysis "bash" 12 days ago Up 12 days 6023/tcp, 6073/tcp, 6800/tcp, 8118/tcp, 8888/tcp, 9050/tcp, 0.0.0.0:32770->8885/tcp nostalgic_euler
In this case, because I remember that I ran docker around 2 days ago, I attach my container by docker attach 6968e. However, usually we forgot this.
What is the best practice to detect the container ID of mine under the situation that there are a lot of containers with the same Image name?
The simple way is to name the containers
docker run --name my-special-container my_account/analysis
docker attach my-special-container
You can store the container ID in a file when it launches
docker run --cidfile ~/my-special-container my_account/analysis
docker attach $(cat ~/my-special-container)
You can add more detailed metadata with object labels, but they are not as easily accessible as names
docker run --label com.rkjt50r983.tag=special my_account/analysis
docker ps --filter 'label=com.rkjt50r983.tag=special'