I agree with Fang that controlling image purge functionality with optional parameters offers the flexibility needed to balance performance and security concerns.
Perhaps there are two API calls where we could implement such an option: /v1/container/post (create) /vi/container/delete That way you could default to either “secure” or “performance”, and optionally select the alternate depending on the value of the parameter you supply when the API is called. Note that Docker (unless forced) will not allow the deletion of a container image until all containers created from that image are also deleted. We will want to be sure we have adequate tests to be sure that related uses are tested, and have exceptions that raise actionable error messages when raised. Let’s not have an “unknown exception” when I try to delete a container, and I get an error when it tries to delete the container image, but can’t because there is another container running that used the same image. Finally, we might also want to allow a user to specify whether untagged parents should be pruned or not (ie: docker rmi —no-prune=true) Adrian On Apr 14, 2015, at 2:31 AM, Fang Fenghua <449171...@qq.com<mailto:449171...@qq.com>> wrote: Indeed image pull be time-consuming. Is it much better to supply a magnum api let end-user can clean image that not used? Clean or not clean is decide by the end-user. Or we can supply a method let end-user can decide whether or not clean image. Date: Mon, 13 Apr 2015 14:51:05 +0800 From: "=?gb18030?B?NDQ5MTcxMzQy?=" <449171...@qq.com<mailto:449171...@qq.com>> To: "=?gb18030?B?b3BlbnN0YWNrLWRldg==?=" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] ?magnum?About clean none use container imag Message-ID: <tencent_1b594e50513691b07d1b8...@qq.com<mailto:tencent_1b594e50513691b07d1b8...@qq.com>> Content-Type: text/plain; charset="gb18030" >From now on magnum had container create and delete api .The container create >api will pull docker image from docker-registry.But the container delete api >didn't delete image.It will let the image remain even though didn't had >container use it.Is it much better we can clear the image in someway? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150413/7072441b/attachment-0001.html><http://lists.openstack.org/pipermail/openstack-dev/attachments/20150413/7072441b/attachment-0001.html%3E>; ------------------------------ Message: 26 Date: Mon, 13 Apr 2015 15:09:18 +0800 From: Jay Lau <jay.lau....@gmail.com<mailto:jay.lau....@gmail.com>> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] ?magnum?About clean none use container imag Message-ID: <CAFyztAG6EOd97Ho5zir7U0Gmywq=J=aerh9wjai-2yswx2e...@mail.gmail.com<mailto:CAFyztAG6EOd97Ho5zir7U0Gmywq=J=aerh9wjai-2yswx2e...@mail.gmail.com>> Content-Type: text/plain; charset="utf-8" Interesting topic, pulling image is time consuming, so someone might not want to delete the container; But for some cases, if the image was not used, then it is better to remove them from disk to release space. You may want to send out an email to [openstack][magnum] ML to get more feedback ;-) 2015-04-13 14:51 GMT+08:00 449171342 <449171...@qq.com<mailto:449171...@qq.com>>: > > > From now on magnum had container create and delete api .The container create > api will pull docker image from docker-registry.But the container delete api > didn't delete image.It will let the image remain even though didn't had > container use it.Is it much better we can clear the image in someway? > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Thanks, Jay Lau (Guangya Liu) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ 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
