[Starlingx-discuss] Docker image list

[Sun, Austin]

Echo this request. Publishing a list of images per release is really helping a lot of developers  especially  who is working behind proxy.

Thanks.
BR
Austin Sun.

From: Curtis [mailto:serverascode at gmail.com]
Sent: Monday, June 24, 2019 7:39 PM
To: Li, Cheng1 <cheng1.li at intel.com>
Cc: starlingx-discuss at lists.starlingx.io; Xu, Chenjie <chenjie.xu at intel.com>
Subject: Re: [Starlingx-discuss] Docker image list



On Mon, Jun 24, 2019 at 2:45 AM Li, Cheng1 <cheng1.li at intel.com<mailto:cheng1.li at intel.com>> wrote:
Hello Starlingxer,

As you know many docker images are pulled during starlingx deployment. It may be fast to pull all these images in America, but it’s very slow in China.
To speed up starlingx deployment, I have set up a private docker registry for which I sync images every night from upstream registries by cron job.
I installed starlingx without using my private docker registry so that I can get the upstream docker image list. Every item in the list is synced every day.

This works fine except that the docker image list changes sometimes. In this case, I would have to collect the image list by deploying without using private docker registry, which is very slow.
So I wonder if it’s possible to publish the docker image list file together with ISO and tarball on CENGN. I know we do sanity tests for each ISO, maybe we can run ‘docker images’ in sanity test to collect the docker image list?


I'd love to see the same thing. For the workshop we did at the last summit I would have to deploy, then note what images were deployed, then download them all. Not automatable. If we could publish a list of images per release that would help immensely. :)

Thanks,
Curtis


Thanks,
Cheng

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io<mailto:Starlingx-discuss at lists.starlingx.io>
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss


--
Blog: serverascode.com<http://serverascode.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190624/aca66cfa/attachment-0001.html>