Docker: kill/stop/restart a container, parameters maintained?

I run a specific docker image for the first time:

docker run [OPTIONS] image [CMD]

  • Ambari 2.2 - exiting with non-zero status code on Ubuntu 14.04 Docker container
  • when mounting volume, directory is empty in docker
  • Run docker without “sudo” in Fedora 24
  • What happens when a volume links an existing populated host and container dir
  • How to assign domain names to containers in docker
  • How to access files downloaded on my windows machine from boot2docker?
  • Some of the options I supply include --link (link with other containers) and -p (expose ports)

    I noticed that if I kill that container and simply do docker start <container-id>, Docker honors all the options that I specified during the run command including the links and ports.

    Is this behavior explicitly documented and can I always count on the start command to reincarnate the container with all the options I supplied in the run command?


    Also, I noticed that killing/starting a container which is linked to another container updates the upstream container’s /etc/hosts file automatically:

    A--(link)-->B (A has an entry in /etc/hosts for B)

    If I kill B, B will normally get a new IP address. I notice that when i start B, the entry for B in A’s /etc/hosts file is automatically updated… This is very nice.

    I read here that --link does not handle container restarts… Has this been updated recently? If not, why am I seeing this behavior?

    (Im using Docker version 1.7.1, build 786b29d)

  • Docker for Mac: Hostname setup for container
  • Setting up our own private docker hub
  • Behat Mink file upload not finding file on submit
  • using kerberos in a container, inside of openshift / kubernetes
  • Using Spinnaker to deploy a Docker image from dockerhub to Aws Eb
  • Is supervisord needed for docker+gunicorn+nginx?
  • One Solution collect form web for “Docker: kill/stop/restart a container, parameters maintained?”

    Yes, things work as you describe 🙂

    You can rely on the behaviour of docker start as it doesn’t really “reincarnate” your container; it was always there on disk, just in a stopped state. It will also retain any changes to files, but changes in RAM, such as process state, will be lost. (Note that kill doesn’t remove a container, it just stops it with a SIGKILL rather than a SIGTERM, use docker rm to truly remove a container).

    Links are now updated when a container changes IP address due to a restart. This didn’t use to be the case. However, that’s not what the linked question is about – they are discussing whether you can replace a container with a new container of the same name and have links still work. This isn’t possible, but that scenario will be covered by the new networking functionality and “service” objects which is currently in the Docker experimental channel.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.