Re: Proposal to mirror Docker images

On jueves, 1 de septiembre de 2016 10:49:15 AM CDT Colin Walters wrote: > On Tue, Aug 16, 2016, at 11:33 AM, Randy Barlow wrote: > > In summary, the proposal is to write a patch for the docker client that > > will give it the capability to accept metalink responses upon docker > > pull operations.

Re: Proposal to mirror Docker images

On Thu, Sep 1, 2016, at 10:49 AM, Colin Walters wrote: > Related to this, I think it'd be useful to target public IaaS (AWS, GCE, etc.) > for inside-infra mirrors. Basically we want Fedora images to hit a S3 bucket > in > the region or equivalent by default for content. This is how Amazon >

Re: [Second Draft] Proposal to mirror Docker images

I've documented this second draft on the wiki[0]. At this time we don't have signing figured out. Since signing could impact the plan, we are stuck on figuring that out before going further. [0] https://fedoraproject.org/wiki/Changes/FedoraDockerRegistry signature.asc Description: This is a

Re: [Second Draft] Proposal to mirror Docker images

On Tue, 2016-09-06 at 13:59 -0400, Randy Barlow wrote: > One thing that may work is to have the Manifest Lists be signed > instead > of the Manifests themselves. The Manifest Lists are the list of > Manifests that are available, one per supported arch. During docker > pull, we can give the client

Re: [Second Draft] Proposal to mirror Docker images

On Wed, 2016-08-24 at 18:25 -0400, Randy Barlow wrote: > Signing > --- > > Patrick raised the question of signing. Docker supported signing > within > the manifest with the schema 1 version, but with schema 2 the > embedded > signatures have been removed in favor of the Notary service[5].

Re: Proposal to mirror Docker images

On Thu, 1 Sep 2016 17:24:50 +0200 Adrian Reber wrote: > > This already happens for EPEL: > > $ curl -s > "https://mirrors.fedoraproject.org/mirrorlist?repo=epel-7=x86_64=52.3.178.0; > | head -2 # repo = epel-7 arch = x86_64 Using preferred netblock > Using Internet2 country =

Re: Proposal to mirror Docker images

On Thu, Sep 01, 2016 at 10:49:15AM -0400, Colin Walters wrote: > > pull operations. We would also need to add support for Docker images to > > > > mirror list and mirror manager. Additionally, we will need a small tool > >

Re: Proposal to mirror Docker images

On Thu, Sep 01, 2016 at 10:49:15AM -0400, Colin Walters wrote: > On Tue, Aug 16, 2016, at 11:33 AM, Randy Barlow wrote: > > > > In summary, the proposal is to write a patch for the docker client that > >

Re: Proposal to mirror Docker images

On Tue, Aug 16, 2016, at 11:33 AM, Randy Barlow wrote: > In summary, the proposal is to write a patch for the docker client that > > will give it the capability

Re: [Second Draft] Proposal to mirror Docker images

On Tue, Aug 30, 2016 at 1:14 PM, Matthew Miller wrote: > On Tue, Aug 30, 2016 at 01:53:23PM -0400, Stephen John Smoogen wrote: >> Do the old ones need to be kept around for GPL and other compliance? > > No, as long as we have a way to trace back from a given image to its

Re: [Second Draft] Proposal to mirror Docker images

On Mon, Aug 29, 2016 at 3:55 AM, Pierre-Yves Chibon wrote: > On Wed, Aug 24, 2016 at 06:25:15PM -0400, Randy Barlow wrote: >> Mirror List >> --- >> >> Users will be pointing their docker clients at Mirror List when they >> docker pull Fedora's Docker images. In order

Re: [Second Draft] Proposal to mirror Docker images

anifest v2, and discussions in >> > #fedora-releng, I would like to propose this second draft of the >> > proposal to mirror Docker images. Thank you for reading, and please do >> > voice your thoughts! >> OK my major concern with mirroring Docker images are the following: &g

Re: [Second Draft] Proposal to mirror Docker images

f the > > proposal to mirror Docker images. Thank you for reading, and please do > > voice your thoughts! > OK my major concern with mirroring Docker images are the following: > 1) How many images? Initially, dozens. Probably growing to the order of 100s. > 2) How large are these image

Re: [Second Draft] Proposal to mirror Docker images

On Mon, 2016-08-29 at 10:55 +0200, Pierre-Yves Chibon wrote: > I am wondering if it would make sense to have a new mirrorlist-docker > that would > be different from the actual/current mirrorlist. It would allow > easier > modifications and evolutions w/o running into the risk of breaking > the

Re: [Second Draft] Proposal to mirror Docker images

On Wed, Aug 24, 2016 at 06:25:15PM -0400, Randy Barlow wrote: > Mirror List > --- > > Users will be pointing their docker clients at Mirror List when they > docker pull Fedora's Docker images. In order for this to work, we will > need to make two changes to Mirror List so that it can

Re: [Second Draft] Proposal to mirror Docker images

Hello! Based on the responses I've received so far, some new information I learned about Docker's Manifest v2, and discussions in #fedora-releng, I would like to propose this second draft of the proposal to mirror Docker images. Thank you for reading, and please do voice your thoughts! Notable

Re: Proposal to mirror Docker images

On Sun, 2016-08-21 at 14:55 -0400, Randy Barlow wrote: > When the docker client attempts to pull, > the first thing it does it to perform a GET /v2/. The registry *must* > respond with a particular header that indicates that it is a Docker > v2 > registry, and include {} as the body response. Due

Re: Proposal to mirror Docker images

On Fri, 2016-08-19 at 12:19 +, Patrick Uiterwijk wrote: > On Tue, Aug 16, 2016 at 3:33 PM, Randy Barlow > > docker > > -- > > > > The most significant work required will likely be modifying the > > docker > > client to enable it to properly handle the metalink responses it > > will be > >

Re: Proposal to mirror Docker images

On Tue, Aug 16, 2016 at 3:33 PM, Randy Barlow wrote: > The docker client typically connects to port 5000. We could run a > second instance of Mirror List on port 5000 if we wanted to isolate it > from the current instance. We can also have the docker client pull from

Re: Proposal to mirror Docker images

> The last piece that is needed is a tool that can create the filesystem > tree that we want to synchronize out to the mirrors. The mirrors only > need to carry manifests and blobs, so the tool needs only to pull these > documents out of the registry that Adam Miller has set up and write them > to

Re: Proposal to mirror Docker images

On Tue, Aug 16, 2016 at 11:24:20AM -0500, Jason L Tibbitts III wrote: > 4) How will this be organized on the master mirrors? It really should >be in a separate rsync module, and the archive (if that happens) >should also be in a separate rsync module. I think this is a good idea, it will

Re: Proposal to mirror Docker images

On Tue, 2016-08-16 at 11:24 -0500, Jason L Tibbitts III wrote: > It would also help to have the following information.  The mirrors > will > need to have this information in order to make informed > decisions.  (I > will also have to make changes to quick-fedora-mirror to > accommodate.) > > 1)

Re: Proposal to mirror Docker images

It would also help to have the following information. The mirrors will need to have this information in order to make informed decisions. (I will also have to make changes to quick-fedora-mirror to accommodate.) 1) How much content will the mirrors need to store? How will this amount change

Proposal to mirror Docker images

During Flock 2016, I had the opportunity to talk with Adam Miller, Dennis Gilmore, and Pierre-Yves Chibon about the technical challenges with distributing Docker images with Fedora's extensive mirror