This question already has answers here:
what is docker run -it flag?
(3 answers)
Closed 12 days ago.
When I containerize my image with "docker run my_image" and "docker run -it my_image"., both works same, but what is the difference ?
The docker run command is used to start a new container from an image. The difference between docker run my_image and docker run -it my_image is in the way they interact with the container.
docker run my_image runs the container in the background, detached from the terminal. The container will continue to run in the background until it is stopped or exits.
docker run -it my_image runs the container in the foreground, attached to the terminal. The -it option allows you to interact with the container using the terminal. This is useful for running commands within the container and observing the output in real-time.
In summary, docker run my_image is used to run a container in the background without interaction, while docker run -it my_image is used to run a container in the foreground and interact with it using the terminal.
I have created one docker container using the following command:
# docker run -itd --name ssh -p "1111:22" <--Image Name-->
When I tried to list normally using command:
I tried also restart and start command but it's not working.
I heard that in case of no --detach in docker run option my terminal is attach to the container, is it this the same as attaching terminal with docker run -it options? What is the difference?
You can start a docker container in detached mode with a -d option. So the container starts up and run in background. That means, you start up the container and could use the console after startup for other commands.
This example runs a container named test using the debian:latest image. The -it instructs Docker to allocate a pseudo-TTY connected to the container’s stdin; creating an interactive bash shell in the container.
docker run --name test -it debian
I want to run multiple containers automatically and create something,
but some images, such as swarm, will automatically stop after run or start.
I already try like that
docker run -d swarm
docker run -d swarm /bin/bash tail -f /dev/null
docker run -itd swarm bash -c "while true; do sleep 1; done"
but 'docker ps' show nothing, and I tried to build Dockerfile by typing:
FROM swarm
ENTRYPOINT ["echo"]
and The image does not run with error message :
docker: Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"exec: \\\"echo\\\": executable file not found in $PATH\"\n".
I can't understand this error... How can I keep swarm container running..?
(Sorry,my English is not good))
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.
However, there is a problem with -d option. Your container immediately stops unless the commands are not running on foreground.
Docker requires your command to keep running in the foreground. Otherwise, it thinks that your applications stops and shutdown the container.
The problem is that some application does not run in the foreground.
In this situation, you can add tail -f /dev/null to your command.
By doing this, even if your main command runs in the background, your container doesn’t stop because tail is keep running in the foreground.
docker run -d swarm tail -f /dev/null
docker ps shows container
Now you can attach your container by using docker exec container_name command
or
docker run -d swarm command tail -f /dev/null
First of all you don't want to mix the -i and -d switches. Either you would like to run the container in interactive or detached mode. In your case in detached mode:
docker run -d swarm /bin/bash tail -f /dev/null
There are also no need to allocate a tty using the -t flag, since this only needs to be done in interactive mode.
You should have a look at the Docker run reference
Docker container does two type of task. One is to perform and exit & other is to run it in background.
To run docker container in background, there are few options.
Run using shell. docker run -it <image> /bin/bash
For continuously running container. docker run -d -p 8080:8080 <image>. Assuming image will expose port 8080 and in listening mode.
It's fine to to a tail on /dev/null, but why not make it do something useful?
The following command will reap orphan processes, so no zombie (defunct) precesses are left floating around. Also some init.d / restart scripts doesn't allow this.
exec sh -c 'while true ;do wait ;done'
You are right docker run -itd swarm ( Without give argument for container( bash -c "while true; do sleep 1; done" ) )works fine .If you pass argument for docker run it will run the command and terminates the container.If you want to run the container permanently first start the container with docker run -itd swarm and check if the container runs or not by docker ps now the container runs , if you want to execute any command in container use docker exec -itd container_name command Remember : Only use the command which not stop the container. bash -c "while true; do sleep 1; done this command will stop the container ( Because this is complete command if we execute in normal terminal it execute and terminate , this type of command also terminates the container ).
I Hope this Helps..
Basically this is the method , but your docker image is swarm so it is different and i don't know about swarm docker image and i am not using that .But after i research about that . First i run the docker swarm image it shows.,
After that i understand we run docker swarm image by using only five commands in picture like create, list manage, join, help . if we run swarm image without command like docker run -itd swarm it takes command as --help . Sorry, But i don't know what is the purpose of swarm image. For more usage check https://hub.docker.com/_/swarm/ .
The answer that i added docker run -itd image tail -f /dev/null is not for swarm image , it is for docker images like ubuntu,fedora, centos.
Just read the usage of swarm image and why it is used .
After if you have any issue post your issue in https://github.com/docker/swarm-library-image/issues
Thank You...
have a container running
docker run --rm -d --name=tmp ubuntu sleep infinity
example of requesting a command from the dorment container
docker exec tmp echo hello from container
notes:
--rm removes the container if it is stopped
-d runs the container in the background
--name=tmp name the container so you control how to denote it
ubuntu pushes a light image to exec your commands
sleep infinity keeps the container dorment
I am running Kurento on debian through Docker with
docker run -d --name kurento -p 8888:8888 kurento/kurento-media-server
That starts the kurento server. Problem is : I need to configure /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini file that runs in docker and I have no idea on how to access it since it runs in background
When I run docker in interactive mode:
docker run -it --name kurento -p 8888:8888 kurento/kurento-media-server
the server runs in foreground, and I cannot do anything except a CTRL+C ( I tried ctrl+Z to put in in BG process)
Any idea ?
If you have to input an initial configuration file, the best way is by using a volume when starting:
docker run -d --name kurento -p 8888:8888 -v /etc/kurento/modules/kurento/:/path/to/your/env/kurento kurento/kurento-media-server
and inside /path/to/your/env/kurento will be your WebRtcEndpoint.conf.ini file
If you just want to jump inside the machine and tinker around, you can 'exec bash':
docker exec -it kurento /bin/bash
Once your container is started and running, you can create a bash session in that container with below command:
docker exec -ti <container_name> bash