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:

  • Why can't I ping docker container?
  • Pushing to Docker Private Organization Repository
  • Docker compose bind container to interface
  • Curl in Docker entrypoint script
  • Update shared volume from data container
  • Docker Compose: deploying different services from docker-compose.yml to different set of hosts
  • $ 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.

  • Mounting a gcePersistentDisk kubernetes volume is very slow
  • Start play framework app from dockerfile
  • Selenium ChromeDriver Failed to load resource: net::ERR_CONNECTION_CLOSED
  • Bad log time in Docker
  • Is docker stateless?
  • What happens if docker container requires kernel features not provided by host?
  • 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.