Re:Intro Guide to Dockerfile Best Practices
by ses1984 on Tuesday July 09, 2019 @10:56AM
(#20392380)
Yeah but why would you build in that kind of tech debt in the first place? It seems a lot of effort to host meta files and keep that available than some other solution that doesn't require internet access.
[ Parent
| on HN ]
Re:Intro Guide to Dockerfile Best Practices
by AnthonBerg on Tuesday July 09, 2019 @12:17PM
(#20393372)
I take it as a temporary measure that will be undone when it's past being experimental.
Re:Intro Guide to Dockerfile Best Practices
by ses1984 on Tuesday July 09, 2019 @08:22PM
(#20398126)
If I were to propose to my team that we install a temporary measure in the form of an additional service that needs availability they would smack me down, because that's a pretty stupid temporary measure.
Re:Intro Guide to Dockerfile Best Practices
by AnthonBerg on Wednesday July 10, 2019 @05:28AM
(#20400410)
Software is generally published online. Docker image repositories are generally online. The very act of building a Docker image pulling in dependencies is generally done online.
It was a deep hack into the entirety of the Docker build chain. This way it was probably possible to publish experimental work-in-progress build features to the world at a faster pace than the official Docker release cycle.
And as pointed out above, the online-only requirement has been lifted already.
The situation is perfectly understandable, and to be commended that people offered to do this work for the betterment of all.