For the vast majority of docker images, the documentation only mention a super long and hard to understand “docker run” one liner.
Why nobody is placing an example docker-compose.yml in their documentation? It’s so tidy and easy to understand, also much easier to run in the future, just set and forget.
If every image had an yml to just copy, I could get it running in a few seconds, instead I have to decode the line to become an yml
I want to know if it’s just me that I’m out of touch and should use “docker run” or it’s just that an “one liner” looks much tidier in the docs. Like to say “hey just copy and paste this line to run the container. You don’t understand what it does? Who cares”
The worst are the ones that are piping directly from curl to “sudo bash”…
Something that always confused me was how docker doesn’t come with compose installed as a core component.
It does now.
docker compose vs docker-compose. Yes I know it’s stupid.
Well today I learned something! I’ve been using docker-compose for 5+ years now and I never happened upon the addition of compose to docker haha.
It’s also the issue with the internet and all the fantastic guides which even if they were written 12 months ago, are already out of date!