instruction: Create a Dockerfile for compose
output: ```dockerfile
  from the Docker API.1.3.2(2015-07-14)Bug fixesWhen there were one-off containers created by running docker-compose run on an older version of Compose, docker-compose run would fail with a name collision. Compose now shows an error if you have leftover containers of this type lying around, and tells you how to remove them.Compose was not reading Docker authentication config files created in the new location, ~/docker/config.json, and authentication against private registries would therefore fail.When a container had a pseudo-TTY attached, its output in docker-compose up would be truncated.docker-compose up --x-smart-recreate would sometimes fail when an image tag was updated.docker-compose up would sometimes create two containers with the same numeric suffix.docker-compose rm and docker-compose ps would sometimes list services that aren't part of the current project (though no containers were erroneously removed).Some docker-compose commands would not show an error if invalid service names were passed in.Thanks @dano, @josephpage, @kevinsimper, @lieryan, @phemmer, @soulrebel and @sschepens!1.3.1(2015-06-21)Bug fixesdocker-compose build would always attempt to pull the base image before building.docker-compose help migrate-to-labels failed with an error.If no network mode was specified, Compose would set it to "bridge", rather than allowing the Docker daemon to use its configured default network mode.1.3.0(2015-06-18)Important notesThis release contains breaking changes, and you will need to either remove or migrate your existing containers before running your app - see the upgrading section of the install docs for details.Compose now requires Docker 1.6.0 or later.ImprovementsCompose now uses container labels, rather than names, to keep track of containers. This makes Compose both faster and easier to integrate with your own tools.Compose no longer uses "intermediate containers" when recreating containers for a service. This makes docker-compose up less complex and more resilient to failure.New featuresdocker-compose up has an experimental new behavior: it will only recreate containers for services whose configuration has changed in docker-compose.yml. This will eventually become the default, but for now you can take it for a spin: $ docker-compose up --x-smart-recreate
  When invoked in a subdirectory of a project, docker-compose will now climb up through parent directories until it finds a docker-compose.yml.Several new configuration keys have been added to docker-compose.yml:dockerfile, like docker build --file, lets you specify an alternate Dockerfile to use with build.labels, like docker run --labels, lets you add custom metadata to containers.extra_hosts, like docker run --add-host, lets you add entries to a container's /etc/hosts file.pid: host, like docker run --pid=host, lets you reuse the same PID namespace as the host machine.cpuset, like docker run --cpuset-cpus, lets you specify which CPUs to allow execution in.read_only, like docker run --read-only, lets you mount a container's filesystem as read-only.security_opt, like docker run --security-opt, lets you specify
  security options.log_driver, like docker run --log-driver, lets you specify a
  log driver.Bug fixesThe output of docker-compose run was sometimes truncated, especially when running under Jenkins.A service's volumes would sometimes not update after volume configuration was changed in docker-compose.yml.Authenticating against third-party registries would sometimes fail.docker-compose run --rm would fail to remove the container if the service had a restart policy in place.docker-compose scale would refuse to scale a service beyond 1 container if it exposed a specific port number on the host.Compose would refuse to create multiple volume entries with the same host path.Thanks @ahromis, @albers, @aleksandr-vin, @antoineco, @ccverak, @chernjie, @dnephin, @edmorley, @fordhurley, @josephpage, @KyleJamesWalker, @lsowen, @mchasal, @noironetworks, @sdake, @sdurrheimer, @sherter, @stephenlawrence, @thaJeztah, @thieman, @turtlemonvh, @twhiteman, @vdemeester, @xuxinkun and @zwily!1.2.0(2015-04-16)docker-compose.yml now supports an extends option, which enables a service to inherit configuration
  ```