4 ms·
you just have to host the recipe and the hash/meta-data c'mon. This is not amateur hour. Hosting the whole thing only made sense for docker because their plan
by ijaeifjzdi 4y ago
you just have to host the recipe and the hash/meta-data
c'mon. This is not amateur hour. Hosting the whole thing only made sense for docker because their plan was always to do this microsoft style play.
If you assume you are either open source or fully closed enterprises, the problem is very, very easy to solve. and cheap. Just relinquish full control of being able to close all the doors for a fee, like they are doing now.
- r3trohack3r 4y agoRerunning a glorified series of bash scripts on every install doesn’t work at any sort of scale. This is why we’ve moved away from configuration over ssh to either: 1) deterministic builds with centralized caches 2) snapshots Docker has some features of (1) but is really (2). You absolutely do not want to download the recipe to build a Docker image instead of the image itself. Further, the base images have no recipe. They are a tarball of a slimmed down pristine base os install.