instruction: Create a Dockerfile for compose
output: ```dockerfile
  from another service in another configuration file. This is really good for sharing common configuration between apps, or for configuring the same app for different environments. Here's the documentation.When using Compose with a Swarm cluster, containers that depend on one another will be co-scheduled on the same node. This means that most Compose apps will now work out of the box, as long as they don't use build.Repeated invocations of docker-compose up when using Compose with a Swarm cluster now work reliably.Directories passed to build, filenames passed to env_file and volume host paths passed to volumes are now treated as relative to the directory of the configuration file, not the directory that docker-compose is being run in. In the majority of cases, those are the same, but if you use the -f|--file argument to specify a configuration file in another directory, this is a breaking change.A service can now share another service's network namespace with net: container:<service>.volumes_
  ```