----- Original Message ----- > On 25/03/15 00:41, Jeremy Eder wrote: > > >> we can overload the /u/centos at index.docker.io for these sort of > >> containers. maybe this doesnt merit a /_/centos instance > >> > >> would that work ? > > > > Can you help me understand the distinction ? > > > /_/CentOS hosts the validated, docker officially accepted ( validated ? > ) images. this is what you get when you say 'docker run centos' > > /u/centos hosts content as username centos. this is what you get with > 'docker run centos/wildfly'. > > /_/centos has a ~ 2 days upload process, including manual intervention > and tests. /u/centos is a docker push target. > > in a nurshell : different levels of trust and process of uploading > containers into.
I'm looking at this from a user perspective. The "official" Library images are typically base images (yes, it has a growing list of non-base images). Centos has an organization[1] where centos/freeipa, centos/mariadb, centos/http etc. images live. This is where I would expect a tools image to land, centos/tools (or whatever we call it). Unfortunately finding the centos organization was not easy for me, either through browse or search. [1] https://registry.hub.docker.com/repos/centos/ > > > -- > Karanbir Singh > +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh > GnuPG Key : http://www.karan.org/publickey.asc > >
