instruction: Create a Dockerfile for compose
output: ```dockerfile
  from the docker-machine config command would
  not be properly interpreted by Compose.Fixed a bug where the connection to the Docker Engine would
  sometimes fail when running a large number of services simultaneously.Fixed an issue where Compose would sometimes print a misleading
  suggestion message when running the bundle command.Fixed a bug where connection errors would not be handled properly by
  Compose during the project initialization phase.Fixed a bug where a misleading error would appear when encountering
  a connection timeout.1.8.0(2016-06-14)Breaking ChangesAs announced in 1.7.0, docker-compose rm now removes containers
  created by docker-compose run by default.Setting entrypoint on a service now empties out any default
  command that was set on the image (i.e. any CMD instruction in the
  Dockerfile used to build it). This makes it consistent with
  the --entrypoint flag to docker run.New FeaturesAdded docker-compose bundle, a command that builds a bundle file
  to be consumed by the new Docker Stack commands in Docker 1.12.Added docker-compose push, a command that pushes service images
  to a registry.Compose now supports specifying a custom TLS version for
  interaction with the Docker Engine using the COMPOSE_TLS_VERSION
  environment variable.Bug fixesFixed a bug where Compose would erroneously try to read .env
  at the project's root when it is a directory.docker-compose run -e VAR now passes VAR through
  ```