Although it’s supposed to be used for multi-container applications you may use it for a service using only one container. You can set your volumes, ports… in YAML sintax and use that file to start your container.
doncicuto actualy suggested a better solution: declare your configuration with a docker-compose.yml.
docker-compose has build in support for env-files, can resolve system variables in place and extend configurations using multiple docker-compose.yml.
If you are not open to it yet: don’t worry, eventualy you will get there
Just to mention it: you could always use make and encapsulate the parsing and starting within the file. professionel setups end up using makefiles combined with swarm/kubernetes configurations, where configurations can be rendered using envsubst or a real template engine.