instruction: Create a Dockerfile for compose
output: ```dockerfile
  from
  writing to stdin during interactive sessions started by run or exec.One-off containers started by run no longer adopt the restart policy of the service,
  and are instead set to never restart.Fixed an issue that caused some container events to not appear in the output of
  the docker-compose events command.Missing images will no longer stop the execution of docker-compose down commands. A warning is
  now displayed instead.Force virtualenv version for macOS CI.Fixed merging of Compose files when network has None config.Fixed CTRL+C issues by enabling bootloader_ignore_signals in pyinstaller.Bumped docker-py version to 3.7.2 to fix SSH and proxy configuration issues.Fixed release script and some typos on release documentation.1.23.2(2018-11-28)Bug fixesReverted a 1.23.0 change that appended random strings to container names
  created by docker-compose up, causing addressability issues.
  NoteContainers created by docker-compose run will continue to use randomly generated names to avoid collisions during parallel runs.Fixed an issue where some dockerfile paths would fail unexpectedly when
  attempting to build on Windows.Fixed a bug where build context URLs would fail to build on Windows.Fixed a bug that caused run and exec commands to fail for some otherwise
  accepted values of the --host parameter.Fixed an issue where overrides for the storage_opt and isolation keys in
  service definitions weren't properly applied.Fixed a bug where some invalid Compose files would raise an uncaught
  exception during validation.1.23.1(2018-11-01)Bug fixesFixed a bug where working with containers created with a version of Compose earlier than 1.23.0
  would cause unexpected crashes.Fixed an issue where the behavior of the --project-directory flag would
  vary depending on which subcommand was used.1.23.0(2018-10-30)Important noteThe default naming scheme for containers created by Compose in this version
  has changed
  ```