[ 
https://issues.apache.org/jira/browse/MESOS-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357288#comment-15357288
 ] 

Kevin Klues commented on MESOS-5401:
------------------------------------

The crux of the issue is that we need to be able consolidate all of the Nvidia 
binaries/libraries into a single volume that we inject into
a docker container. The goal is to let users leverage the nvidia Docker images 
(https://hub.docker.com/r/nvidia/) without any added effort on their behalf. 
Using docker they are able to launch containers from these images by simply 
running `nvidia-docker run ...` (i.e. they are
unaware that a magic volume is being injected on their behalf). On Mesos we 
want the experience to be similar.

The information at the link below should make things a bit more clear as to why 
this is necessary:

https://github.com/NVIDIA/nvidia-docker/wiki/NVIDIA-driver.

We originally planned on building this functionality as an isolator module, but 
there some some limitations with the current isolator interface that prohibit 
us from doing this properly. Building it as an isolator module would also mean 
that it couldn't be shared by the docker containerizer (which we plan to add 
support for in the future).

> Add ability to inject a Volume of Nvidia GPU-related libraries into a docker 
> container.
> ---------------------------------------------------------------------------------------
>
>                 Key: MESOS-5401
>                 URL: https://issues.apache.org/jira/browse/MESOS-5401
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Kevin Klues
>            Assignee: Kevin Klues
>
> In order to support Nvidia GPUs with docker containers in Mesos, we need to 
> be able to consolidate all Nvidia libraries into a common volume and inject 
> that volume into the container.
> More info on why this is necessary here: 
> https://github.com/NVIDIA/nvidia-docker/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to