[scl.org] Image naming for centos-based images

[Michal Fojtik]

I think one of the main reason (AFAIK) we used "-rhel7" and "-centos7"
suffixed for the images
was that we simply used one repository ("openshift/") and we needed to have
a way to distinguish
between rhel7 and centos7 images.

Now, when we are pushing the images to "centos/" namespace on DockerHub,
this is not longer required
I think, because "centos/ruby-22-centos7" sounds just weird :-)

Similar to the RHEL7 images that we will ship via registry.access.redhat.com
where we push only RHEL7 based
images, we can relax the suffix.

Are there any other concerns or reasons why keeping the suffixes is bad
other than it "looks weird" and it is
"redundant" ?

  -- Michal



On Thu, Oct 22, 2015 at 11:41 AM, Josef Stribny <jstribny at redhat.com> wrote:

>
> We're trying to make them consistent at least in the community space,
> without making them needlessly complex or redundant. To your question, I
> would posit that in the community space, it doesn't matter. The container
> users simply aren't interested in whether they're based on fedora 21 or
> fedora 22. The users are after the application, not the OS. The OS itself
> is largely invisible in the container ecosystem except as a host or base
> container.
>
>
>
> I agree people are after an application, but I actually don't like not
> knowing the underlying system and
> I even think that CentOS has a good reputation and can draw attention to
> these images...
>
> Josef
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/env-and-stacks/attachments/20151022/a6687d9c/attachment-0001.html>