2 ms·
The dependency issues are solved if you reuse a given docker image; as you said. Yes, the procedure of generating the image (Dockerfile) is basically a glorifi
by ithkuil 13y ago
The dependency issues are solved if you reuse a given docker image; as you said.
Yes, the procedure of generating the image (Dockerfile) is basically a glorified installation script.
But I don't understand why you use the properties of the image creation tool to refute runtime properties of docker images.
EDIT: like if when discussing the properties of a perfect headache free binary package management system, you mention that the code is still not guaranteed to be the same because when the packages are built, two builds of the same package could be slightly different. The purpose of the binary packaging scheme is to use the built artifact. Repeatable builds are a secondary goal.
- IanCal 13y ago> But I don't understand why you use the properties of the image creation tool to refute runtime properties of docker images. I'm not, my concern is that the language used suggested that having a Dockerfile meant that if it builds for one person it would build for all when this isn't the case. That's not a problem with docker, as it's not something docker is trying to (or claiming to) solve. I'm worried that some people might think it is, so thought I'd post here to clarify things.