The docker-compose approach means you only need to figure it out once. If you're going things like mounting volumes, opening ports, etc your docker run incantation can become complex.
Defining a docker-compose saves you time in the future ensuring all of your requirements are saved in your docker-compose.yml and you only have to run docker-compose up to get your server running.
Got you. I was curious to why docker created that compose file instead of just expecting the users to run docker run command. Your reply answered that question.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The docker-compose approach means you only need to figure it out once. If you're going things like mounting volumes, opening ports, etc your docker run incantation can become complex.
Defining a docker-compose saves you time in the future ensuring all of your requirements are saved in your docker-compose.yml and you only have to run docker-compose up to get your server running.
Nice.
Got you. I was curious to why docker created that compose file instead of just expecting the users to run docker run command. Your reply answered that question.