why not just allow a prefix to be added to the container name? you can then have a container named: foo/mycontainer
and the prefix could be set to mylocalserver.org:8080: mylocalserver.org:8080/foo/mycontainer Then if the site needs local only containers, they can set up a local repo. Be it a stand alone docker registry, the docker datacenter product, artifactory with the docker plugin, etc. Thanks, Kevin ________________________________ From: 王华 [wanghua.hum...@gmail.com] Sent: Monday, April 18, 2016 7:57 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Magnum]Cache docker images Hi all, We want to eliminate pulling docker images over the Internet on bay provisioning. There are two problems of this approach: 1. Pulling docker images over the Internet is slow and fragile. 2. Some clouds don't have external Internet access. It is suggested to build all the required images into the cloud images to resolved the issue. Here is a solution: 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. Any advice for this solution or any better solution? Regards, Wanghua
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
