Lets say I ran the following command: docker run ubuntu touch /tmp/file And now I have stopped container with file in tmp. How can I run other command in this container? I know about commit but I do not want to create new image for every new command. It would be nice to have ability to create na…

Oh, no. It can run only the same command: $ docker run --name cont3 ubuntu echo foo foo $ docker start -a cont3 cont3 foo $ docker start -a cont3 echo bar 2014/11/07 19:57:22 You cannot start and attach multiple containers at once. $

yup, exactly - thats why I mentioned docker exec

Sorry, but I can’t figure out how to use it: $ docker run --name mycont4 ubuntu echo one one $ docker exec mycont4 echo two 2014/11/10 13:24:06 Error response from daemon: Container mycont4 is not running $ docker start mycont4 mycont4 $ docker exec mycont4 echo two 2014/11/10 13:24:24 Error respon…

Ah, I think I see what is happening. In your example, the echo one command exits immediately, which stops the container. docker exec only works with currently running containers. If you want to take the resulting image, and run another command, you will need to commit that and start another contai…

essentially, yes, you need to make your container long running, even if its waiting forever - most times, I tail -f /var/log/something to keep it running - if i don’t have a service to run. in @programmerq ’s example above, your exec’d shell will exit whenever the container does - so in this case, w…

and then inspired by both of you - https://github.com/docker/docker/pull/9082

This is madness. I hope in the future there will be way to do it without any tail/sleep/commit. Or there is any valuable reason for not doing this possible?

Containers are indeed process-centric. Once that process exits, the container is done. having the ability to commit is docker’s way of taking the resulting state from that process and preserving it. This is a key difference between containers and say, a virtual machine. Would you be willing to sha…

mmm, ok, There is a fundamental reason why docker containers work like this. Containers are a set of configuration kernel ‘settings’ that are placed on the application you are running. This means that as far as the Linux kernel is concerned, the container doesn’t exist unless the container’s PID1 i…

Run command in stopped container

Docker Engine General

svendowideit (Sven Dowideit) November 6, 2014, 12:19am 2

in the bash example, because you’re starting the same program, you can do docker start -ai mycont

but in general, no, you’d need to start the container again, (which resumes from where you left off) and then docker exec something in it.

Topic		Replies	Views
Basic question about starting and restarting containers General	14	13543	July 19, 2018
How to limit to run in the same container General	4	2709	June 30, 2015
Docker run and then restart General docker	1	1503	March 14, 2018
How to persist an exited container General	5	11999	November 22, 2017
Commit container, stop and run General	2	1930	August 14, 2015

Run command in stopped container

Related topics