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:

  • Docker nodejs not found
  • Docker blocking outgoing connections on high load?
  • docker-runc not installed on system
  • Concourse cant put docker image to local repo, not a vaild repository/tag
  • Java Development in Dockerized environment: Debugging And hot code reload
  • Elastic Beanstalk with Docker deployment failure
  • $ 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.

  • Best workflow for developing and debugging - initially deploy in a docker environment
  • Lucee 5, Nginx, and Docker Compose not finding sample index.cfm file
  • container is in waiting state, kubernetes, docker container
  • udp traffic with Iperf for haproxy
  • Docker instance cannot run images anymore and unable to reclaim free space
  • Docker + WerckerCi: Tag not found
  • 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.