Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Package Request: nvidia-docker
Date: Mon, 20 Jun 2022 19:52:08 +0200	[thread overview]
Message-ID: <20220620175208.Og4wTbkYsLJN3yR7trzw08tK8waK6WcbSblGuJCeNZ0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11084@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 957 bytes --]

Closed issue by voidlinux4life on void-packages repository

https://github.com/void-linux/void-packages/issues/11084

Description:
https://github.com/NVIDIA/nvidia-docker

NVIDIA designed NVIDIA-Docker in 2016 to enable portability in Docker images that leverage NVIDIA GPUs. It allowed driver agnostic CUDA images and provided a Docker command line wrapper that mounted the user mode components of the driver and the GPU device files into the container at launch.

https://devblogs.nvidia.com/gpu-containers-runtime/

The list of prerequisites for running nvidia-docker 2.0 is described below.
For information on how to install Docker for your Linux distribution, please refer to the Docker documentation.
- GNU/Linux x86_64 with kernel version > 3.10
- Docker >= 1.12
- NVIDIA GPU with Architecture > Fermi (2.1)
- NVIDIA drivers ~= 361.93 (untested on older versions)

https://github.com/nvidia/nvidia-docker/wiki/Installation-(version-2.0)

      parent reply	other threads:[~2022-06-20 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11084@inbox.vuxu.org>
2022-05-01 19:36 ` nuxion
2022-05-01 19:53 ` nuxion
2022-06-20 17:52 ` classabbyamp [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220620175208.Og4wTbkYsLJN3yR7trzw08tK8waK6WcbSblGuJCeNZ0@z \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).