3 ms·
You encounter the same kind problem whenever you want to use Docker with anything that needs a compilation step. Even with front-end development you run into th
by Ruphin 12y ago
You encounter the same kind problem whenever you want to use Docker with anything that needs a compilation step. Even with front-end development you run into the same sort of issues with packaging for production (css preprocessors, coffeescript, 6to5 and such).
Some standardisation in this area would be nice, but the problem can be solved rather trivially by using a separate container with all the tools for the build process, and placing the build product into a lean production image. This process is easy to automate/script, and I don't feel that there is much gain from having some encompassing spec or standard that has to consider all the edge cases and is more complex than necessary as a result.
- bmurphy1976 12y agoI just don't see the problem here. Docker is a compiler (docker build), Dockerfiles are source code, and Docker images are binary artifacts. We already have tools that manage this for us: make, cmake, nmake, rake, scons, etc. People need to get over their fear of build tools and use them. This is exactly the kind of problem they solve. Make IS the standard.