Do not hesitate to contribute then...
back
1 comments
> Do not hesitate to contribute then...
This info is quite literally made available by Docker itself in the form of it's official best practices guide, which exists for years now.
https://docs.docker.com/develop/develop-images/dockerfile_be...
How is anyone publishing a so-called best practices guide when they aren't even aware of the stuff covered by the official best practices guide?
Because they can post something wrong, get the real experts on HN to fix it, then they can use their now awesome repository to sell consultancy service as one of the biggest Docker experts in the world.
:-)
You're hastily assuming that they "aren't aware" when they could have simply chosen to avoid redundancy.