4 ms·
#3: You could very well build a deb with docker (compile from source and package it) and then use that deb subsequently in other containers. Docker can be used
by wernerb 12y ago
#3: You could very well build a deb with docker (compile from source and package it) and then use that deb subsequently in other containers. Docker can be used in CI/CD processes very well. If that is the case, I like the way that Dockerfiles give me complete transparency over the build process, which manual building perhaps does not.
This point clearly states "If you compile code from source during your build" then you should clean the sources.
- akerl_ 12y agoMy apologies for being unclear: I'm saying that in the case where you're building from source during the build of your service container, you're almost always better off building from source in a separate container and then either turning that into a deb or other consumable format.
- amouat 12y agoMaybe. But you do lose some transparency and repeatability - it becomes harder for others to understand and use your Dockerfile. They suddenly have to either download or recreate whatever debs/tarballs etc you've used. I think the real problem is that Dockerfiles aren't expressive enough yet. At the very least we need a more user friendly method to run several commands in single layer.