I have my customer Docker container on a CoreOS OS host. I start my container using the docker run command as. follows:
docker run -d --restart always --net=host -p 8080:8080 --log-opt max-size=2mb my_docker_hub_accountname/imagename
And when I reboot the host I always see multiple images being run when I run the following command:
user#coreos-1 ~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4ac46db4a58c 3fa7e73d544d "java -jar /code/kec…" 7 days ago Up Less than a second lucid_aryabhata
da5392c136e9 7d996239c21c "java -jar /code/kec…" 7 days ago Up Less than a second awesome_jackson
15bcc4cfe26b 7d996239c21c "java -jar /code/kec…" 4 weeks ago Up Less than a second fervent_colden
f050f55bea3c 7d996239c21c "java -jar /code/kec…" 4 weeks ago Up Less than a second condescending_poincare
31e00707ddff 7d996239c21c "java -jar /code/kec…" 4 months ago Up Less than a second awesome_curran
user#coreos-1 ~
Is there a way to control so that I only have 1 image running instead of multiple images by the Docker container?
I was able to resolve this in one way.
I searched for all container using command:
docker ps -a
I had to remove all the other containers that were previously run using
docker rm $container_id
Now I only 1 docker image running in a container. I reboot and I only see 1 container running.
hope it helps another docker user.
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've started multiple container services using docker-compose with following command -
docker-compose up -d --scale cluster-service=3
This starts three container services -
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
87b60bd2554c xxx.xxx.xxx.xxx:5000/cluster-service:1.1.1 "java -cp cluster-se…" 7 minutes ago Up 7 minutes 0.0.0.0:9077->47100/tcp, 0.0.0.0:9076->47500/tcp testcluser_cluster-service_1
b631a656f8ae xxx.xxx.xxx.xxx:5000/cluster-service:1.1.1 "java -cp cluster-se…" 7 minutes ago Up 7 minutes 0.0.0.0:9075->47100/tcp, 0.0.0.0:9074->47500/tcp testcluser_cluster-service_2
f3aeb9541fe9 xxx.xxx.xxx.xxx:5000/cluster-service:1.1.1 "java -cp cluster-se…" 7 minutes ago Up 7 minutes 0.0.0.0:9073->47100/tcp, 0.0.0.0:9072->47500/tcp testcluser_cluster-service_3
In Jenkins pipeline, using shell script, I want to get container ids in the cluster. How can I achieve this with shell script?
Utilise awk to filter on the name and so:
docker ps | awk '$NF~/cluster_service/ { print $1 }'
Check to see if the last space separated field ($NF) matches "cluster-service" If it does, print the container ID (field 1)
Actually using -q option in docker ps command, it only prints container ids:
docker ps -q
Or to get container id of some specific name use:
docker ps -q --filter=name=xxx.xxx.xxx.xxx
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
So I just updated Docker on my Mac and getting adjusted to Docker seems to be quite challenging and confusing.
A few weeks ago, I was able to mind port 8834 on the docker container to port 8834 on my local host by running the following commands (this is my command line history):
8450 docker attach -p 8834:8834 compassionate_chandrasekhar
8452 docker start -p 8834:8834 compassionate_chandrasekhar
Today, if I try to do the same thing, the following happens:
[user:test.local:]$ docker container ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
225146ec71d6 myuser/kali:kali "/usr/bin/zsh" 9 minutes ago Exited (0) 2 minutes ago agitated_fermat
e4389cac288a myuser/kali:kali "/usr/bin/zsh" 2 weeks ago Exited (255) 2 weeks ago suspicious_hypatia
265f2c9215c5 myuser/kali:kali "/usr/bin/zsh" 2 weeks ago Exited (0) 2 weeks ago hungry_poincare
34b36b4d8a7e myuser/kali:kali "/usr/bin/zsh" 2 weeks ago Created amazing_stonebraker
followed by:
[user:test.local:]$ docker start -p 8834:8834 agitated_fermat
unknown shorthand flag: 'p' in -p
See 'docker start --help'.
What am I doing wrong? Extremely confusing
Publishing ports can be done only with newly created containers not existing containers. So you need to stop the container and create a new one with the port you need
Today I was grabbing a Jenkins/Docker-tutorial, and got a similar error.
They do say to start the container the following way, but I got the same error as you:
docker run --name jenkinsci -p 8080:8080 jenkins/jenkins:lts
=> "unknown shorthand flag: 'p' in -p"
When I put the "name"-tag at the end I no longer get the error, and it downloads the container.
docker run -p 9090:8080 jenkins/jenkins:lts --name jenkinsci
It now tells me it does not recognize the option "--name"-tag after downloading.
Without "--name" the container runs.
(Tutorial link: https://medium.com/#gustavo.guss/quick-tutorial-of-jenkins-b99d5f5889f2)
I am trying to run a container based on the debian:stretch image, but this does not work:
docker container run --detach debian:stretch
outputs:
7976eb7074289a741a2b183634345fc8519359cba4d543c03b0a6d4e5d7e0d53
And
docker ps -a
outputs:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7976eb707428 debian:stretch "bash" 3 seconds ago Exited (0) 2 seconds ago vigorous_lumiere
Whereas it works well with the latest nginx image:
docker run --detach nginx:latest
53ed18b5d1a7c72aa92bab0ca679269514db79f31a1d3759c2e25c7fdb1e82ff
docker ps -a
outputs:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
53ed18b5d1a7 nginx:latest "nginx -g 'daemon of…" 2 seconds ago Up 2 seconds 80/tcp admiring_hawking
7976eb707428 debian:stretch "bash" About a minute ago Exited (0) About a minute ago vigorous_lumiere
Why does the container based on the debian:stretch image that I am instantiating does not work?
Does this come from the debian image?
I am running Docker version 18.09.1, build 4c52b90 on Ubuntu 16.04 LTS
Your container literally doesn’t do anything: it starts a shell, but since it’s running as a background process and doesn’t have anything on its stdin, it immediately exits.
You should read the official Docker tutorial on building and running custom images. Generally you should work by building your application into a custom image, setting up that image’s default CMD to run your application, and using docker build and docker run (or a tool like Docker Compose) to run the assembly. There’s not much point in running a plain Linux distribution container.
(Also remember that it’s extremely routine to docker rm containers, and so anything you do in an interactive shell in a container is very likely to get lost.)