This comment shows a remarkable lack of curiosity. You're not the least bit interested to know why so many people find tools like Docker to be valuable?
Docker has its advantages, but the approach also has a lot of disadvantages which are not so obvious to junior developers.
Isolation seems fun, but the interfaces (Unix sockets where anything goes) are extremely brittle. Version management seems simple at first, but will become horrible once old containers offer no upgrade path in the future, or when the free hubs from today will become tomorrow's subscription model.
I'm not advocating for PHP, but it sure made deployment of several websites on one machine extremely simple. Eventually version management destroyed some of the fun, which will probably happen with Docker containers as well, given enough time.
Java's application servers were initially also hailed with similar enthusiasm as Docker containers, and look at the complicated mess that has become.
One of the things that bit one of our teams of developers for about 6 years was the Docker Hub pull limit -- poor configuration (established in the early days of the project), and no caching would occasionally break our builds for a day when we hit the pull limit (because of course lets base our multi-million $$ project on a commercial third-party that we have no contractual arrangement with). Encouraging them to get a proper tech lead to sort out these things was a major win for me.