3 ms·
> Your suggestion of doing pip install has the same problem Recalling that I am speaking in a Dockerfile context, no it doesn't. The 'pip install' runs once, o
by bboreham 9y ago
> Your suggestion of doing pip install has the same problem
Recalling that I am speaking in a Dockerfile context, no it doesn't. The 'pip install' runs once, on my machine when I create the Docker image.
Thank you for the detailed explanation. You have clarified that "just build a deb" is an entirely different exercise.
- yebyen 9y agoAbsolutely. The pip install command is perfect for a Dockerfile where your entire filesystem state is captured and snapshotted. It is a poor way to build a deb, where dependencies are supposed to be explicit and user-pinnable. That's all! :) Thanks for writing back. (In the Heroku deb example, you can't even guarantee that you are going to get the version back from the server that the deb file says it contains. That's probably by design, because Heroku does not intend to break backwards compatibility with new releases of the client, and wants to force upgrades so that they know that you have the latest version of the client at all times.)