Re: [atomic-devel] Tools container for Fedora and CentOS

[Jim Perrin <jperrin centos org>]

On 03/27/2015 10:15 AM, Jeremy Eder wrote:
> 
> 
> ----- Original Message -----
>> From: "Karanbir Singh" <mail-lists karan org>
>> To: "Jeremy Eder" <jeder redhat com>
>> Cc: atomic-devel projectatomic io, "Langdon White" <lawhite redhat com>
>> Sent: Thursday, March 26, 2015 4:43:35 PM
>> Subject: Re: [atomic-devel] Tools container for Fedora and CentOS
>>
>> 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 can't imagine why it takes 2 days, but I think the base containers we're shipping with Atomic should probably go in the more official location (so, *-tools/rsyslog/sadc).  Any hope of automating this as part of the 2-4-6 plan?


This takes roughly 2 days because we submit a pull request, and from
that point it's up to the docker maintainers to pull the images in,
validate them, and accept them. We can automate most of it, but we still
rely on someone else at the other end. Once they accept the PR there's
still generally a bit of lag before they're available.




-- 
Jim Perrin
The CentOS Project | http://www.centos.org
twitter: @BitIntegrity | GPG Key: FA09AD77