Why is “docker start” outputting the name of the container?

I have a small minimal test container made using the ruby image. The ruby script is simple, and outputs the single string “Twitter”.

When I first run the image and create the container, I get this output:

  • Getting connection reset by peer error while using docker on Ubuntu 14.04
  • docker cp doesn't work for this mysql container
  • Deploy-time commands inside Docker on Elastic Beanstalk
  • Unable to access hosted app from docker in Windows
  • Failed to run a script using IntelliJ plugin for docker deplyment
  • fleetctl load hello.service hangs
  • $ docker run -it --name my-running-script my-ruby-app

    Great so far – the script completes and the container exits.

    But when I try to start it again, it first outputs the name of the container:

    $ docker start -a my-running-script

    What is causing this output, and how can I get it to stop? (It’s printed on stdout, and redirecting stderr doesn’t help.)

    I don’t know if it’s relevant, but this is running on OS X using boot2docker.

  • Calabash android.util.AndroidException: INSTRUMENTATION_FAILED
  • Installing ssh-keyscan on Alpine linux?
  • Using docker for unit test
  • docker file not found
  • Port forwarding in when running a Tomcat Docker in an AWS Elastic Beanstalk application
  • Docker - OS X forward localhost 22 port to container 2022 port
  • One Solution collect form web for “Why is “docker start” outputting the name of the container?”

    This is the expected behavior for docker start. Then you can do things like assign the containerID to a variable, etc.

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