I saw discussion in other issues of adding an option to docker-compose down to specify a service, similar to docker-compose stop [SERVICE_NAME]. Is this something that would be useful?
No, that doesn't make any sense for down.
To expand:
down is a project-level operation. It removes containers, but also networks and (potentially) volumes. How would these additional resources be handled in a single service scenario? There is no good, intuitive answer.
If people want to remove a single service, rm -f -s service already does that.
Thanks for the explanation! I'm currently in a virtualization class and part of the class is contributing to open source so I've been looking for issues that would be useful to implement if you have any suggestions.