[
https://issues.apache.org/jira/browse/MESOS-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576122#comment-14576122
]
Ian Downes commented on MESOS-2824:
-----------------------------------
Yes, I agree that this is specific to a single large image (for which the bind
backend is suitable for....) but this should be generalized to multiple images
and furthermore, to not just at slave startup but at any time, perhaps under
the direction of frameworks.
> Support pre-fetching default container image on slave startup
> -------------------------------------------------------------
>
> Key: MESOS-2824
> URL: https://issues.apache.org/jira/browse/MESOS-2824
> Project: Mesos
> Issue Type: Improvement
> Components: isolation
> Affects Versions: 0.23.0
> Reporter: Ian Downes
> Priority: Minor
>
> Default container images can be specified with the --default_container_info
> flag to the slave. This may be a large image that will take a long time to
> initially fetch/hash/extract when the first container is provisioned. Add
> optional support to start fetching the image when the slave starts and
> consider not registering until the fetch is complete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
