On 11/06/2017 03:57 AM, Giuseppe Scrivano wrote:Hi,
I'd like to find a better place where to move the system container[1]
images that I am currently building under docker.io/gscrivano.
CRI-O and Docker them are already used by the OpenShift installer to get
the latest version available.
Are you saying the openshift installer uses docker.io/gscrivano now?
My preference is to move these images under "docker.io/projectatomic".
We can't use the Fedora or CentOS registries since we want to build
these images automatically. The downstream registries will be used only
for a subset of these images.
I understand that we want upstream images for "latest" content in an upstreamrepository but we have to be careful that people know they shouldn't use it inproduction or otherwise rely on these images long term. I think putting them underprojectatomic/ on docker hub might not be clear enough. Ideas:- create a projectatomic-devel organization and put them under there- put them under projectatomic/ but add devel or upstream in the name of each image.Openshift has a set of images they put out to the hub but they also have ateam of people that do release engineering. One option would be to try toget them to agree to own the images and pushes to docker hub under the openshiftnamespace.
We’ll probably need to do this for origin and centos no matter what.
The goal is to build the images automatically on every PR merged.
Occasional builds (maybe daily?) will prevent to miss changes in the
base layers or in the installed rpms.
Having the latest build pushed automatically to a registry is super useful, but mostly for the developers, not as much for users.I really don't want someone reading a blog post where the author uses these imagesand the reader then running them forever. Having "devel" in the name of the image URI will certainly help with that. Maybe I'm being too difficult.
Thoughts?
Thanks,
Giuseppe
[1] https://github.com/projectatomic/atomic-system-containers
|