The problem with these kind of Docker "recipe books" is users very quickly build up an unmanageable number of containers, images, networks, volumes etc. on their Docker hosts. When these users inevitably run into unexpected behaviour (or run out of disk space) their only solution is to "destroy the world" with some other recipe like a "docker prune".

I see similar things with git users who only learn recipes. I die a little inside every time I see someone fix their problems by deleting and recloning the repo because that's what it says to do on "ohshitgit.com".