<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
hi hello again<br>
<br>
I believe you are talking about this bp
<a class="moz-txt-link-freetext" href="https://blueprints.launchpad.net/magnum/+spec/cache-docker-images">https://blueprints.launchpad.net/magnum/+spec/cache-docker-images</a><br>
then ignore my previous reply, that may another topic to solve
network limited problem.<br>
<br>
I think you are on the right way to build docker images but this
image could only bootstrap by cloud-init, without cloud-init<br>
the container image tar file are not loaded at all, but seems this
may not be the best way.<br>
<br>
I'v suggest that may be the best way is we pull docker images while
building atomic-image. Per my understanding, the<br>
image build process is we mount the image to read/write mode to some
tmp directory and chroot to to that dircetory,<br>
we can do some custome operation there.<br>
<br>
I can do a try on
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
the build progress(guess rpm-ostree should support some hook
scripts)<br>
<br>
<br>
<div class="moz-cite-prefix">On 2016年04月19日 11:41, Eli Qiao wrote:<br>
</div>
<blockquote cite="mid:5715A906.7040006@intel.com" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
@wanghua<br>
<br>
I think there were some discussion already , check <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://blueprints.launchpad.net/magnum/+spec/support-private-registry"><a class="moz-txt-link-freetext" href="https://blueprints.launchpad.net/magnum/+spec/support-private-registry">https://blueprints.launchpad.net/magnum/+spec/support-private-registry</a></a><br>
and
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<a moz-do-not-send="true" rel="nofollow"
href="https://blueprints.launchpad.net/magnum/+spec/allow-user-softwareconfig"
style="max-width: 60em; color: rgb(0, 51, 170); text-decoration:
none; font-family: sans-serif; font-size: 12px; font-style:
normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: 18px; orphans: auto;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255);">https:/<wbr style="max-width: 60em;">/blueprints.<wbr
style="max-width: 60em;">launchpad.<wbr style="max-width:
60em;">net/magnum/<wbr style="max-width: 60em;">+spec/allow-<wbr
style="max-width: 60em;">user-softwareco<wbr style="max-width:
60em;">nfig</a><br>
<br>
<div class="moz-cite-prefix">On 2016年04月19日 10:57, 王华 wrote:<br>
</div>
<blockquote
cite="mid:CAH5-jC9+p4OJuAXbCt-wS0nXUccmWJ9=vvBxBJej0R0GOr4umw@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div dir="ltr">Hi all,
<div><br>
</div>
<div>
<div>We want to eliminate pulling docker images over the
Internet on bay provisioning. There are two problems of
this approach:</div>
<div>1. Pulling docker images over the Internet is slow and
fragile.</div>
<div>2. Some clouds don't have external Internet access.</div>
<div><br>
</div>
<div>It is suggested to build all the required images into
the cloud images to resolved the issue.</div>
</div>
<div><br>
</div>
<div>Here is a solution:</div>
<div>We export the docker images as tar files, and put the tar
files into a dir in the image when we build the image. And
we add scripts to load the tar files in cloud-init, so that
we don't need to download the docker images.</div>
<div><br>
</div>
<div>Any advice for this solution or any better solution?</div>
<div><br>
</div>
<div>Regards,</div>
<div>Wanghua</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best Regards, Eli Qiao (乔立勇)
Intel OTC China</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best Regards, Eli Qiao (乔立勇)</pre>
</body>
</html>