4 ms·
There's nothing about this that excludes that work as well. But, there's nothing to say that the upstream distro would accept the changes. Google has more stri
by TheIronYuppie 8y ago
There's nothing about this that excludes that work as well.
But, there's nothing to say that the upstream distro would accept the changes. Google has more stringent requirements that a general distro, and you're choosing to follow those requirements (at the benefit of Google's automated scanning). It's totally your choice.
Disclosure: I work at Microsoft on Azure.
- cpuguy83 8y ago> But, there's nothing to say that the upstream distro would accept the changes If upstream didn't accept it, then it shouldn't be masquerading as what upstream is... which is what changing `FROM $image` to point to Google's image does. > and you're choosing to follow those requirements From what I gathered from the article, Google is changing the meaning of `FROM $image` to mean Google's build of the image. There is no choice in the matter outside of using Google's services. Disclosure (and sorry for not mentioning in the original comment, I've updated): I work at Microsoft on Azure, and formerly at Docker on the core engine.
- dlor 8y agoNothing is changing with FROM - not sure what gave you that impression. We're simply offering some new base images people can choose to use if they want to. These also happen to be the ones that have been in use by some of our "more serverless" offerings, where users don't get to supply a Dockerfile, for some time now.
- cpuguy83 8y ago> As long as the FROM field in your Dockerfile points to `$distro:latest` from Cloud Marketplace I read this perhaps the wrong way, in which case I apologize on that front.