Skip to content
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.

Deprecation Notice with CUDA 11.3.0 #1745

Closed
Overcraft90 opened this issue Apr 11, 2023 · 4 comments
Closed

Deprecation Notice with CUDA 11.3.0 #1745

Overcraft90 opened this issue Apr 11, 2023 · 4 comments

Comments

@Overcraft90
Copy link

Overcraft90 commented Apr 11, 2023

The template below is mostly useful for bug reports and support questions. Feel free to remove anything which doesn't apply to you and add more information where it makes sense.

Also, before reporting a new issue, please make sure that:


1. Issue or feature description

While running a tool (DeepVariant) which leverages GPU acceleration, I get prompted the following

==========
== CUDA ==
==========

CUDA Version 11.3.0

Container image Copyright (c) 2016-2022, NVIDIA CORPORATION & AFFILIATES. All rights reserved.

This container image and its contents are governed by the NVIDIA Deep Learning Container License.
By pulling and using the container, you accept the terms and conditions of this license:
https://developer.nvidia.com/ngc/nvidia-deep-learning-container-license

A copy of this license is made available in this container at /NGC-DL-CONTAINER-LICENSE for your convenience.

*************************
** DEPRECATION NOTICE! **
*************************
THIS IMAGE IS DEPRECATED and is scheduled for DELETION.
    https://gitlab.com/nvidia/container-images/cuda/blob/master/doc/support-policy.md

I made sure to follow the instruction as per here; however, for some reason, I'm not getting the latest version for the NVIDIA Toolkit Container used by Docker.

If relevant, how can I safely update to the latest stable version?

2. Steps to reproduce the issue

sudo docker run --gpus 1 
--workdir path/to/DeepVariant 
--mount "type=bind,src=path/to/DeepVariant,dst=path/to/DeepVariant" 
google/deepvariant:"1.5.0-gpu"
/opt/deepvariant/bin/run_deepvariant 
--model_type=WGS 
--ref=path/to/DeepVariant/input/GRCh38_snarls_removed.fna 
--reads=/path/to/DeepVariant/input/HG002_sorted.bam 
--output_vcf=path/to//DeepVariant/output/HG002-output.vcf.gz 
--output_gvcf=/path/to/DeepVariant/output/HG002-output.gvcf.gz 
--num_shards=16

3. Information to attach (optional if deemed irrelevant)

  • [nvidia-container-info.log] Some nvidia-container information: nvidia-container-cli -k -d /dev/tty info
  • [5.19.0-38-generic] Kernel version from uname -a
  • [none] Any relevant kernel output lines from dmesg
  • [nvidia-smi-a.log] Driver information from nvidia-smi -a
  • [docker_version.log] Docker version from docker version
  • [nvidia_packages.log] NVIDIA packages version from dpkg -l '*nvidia*' or rpm -qa '*nvidia*'
  • [nvidia-container-library.log] NVIDIA container library version from nvidia-container-cli -V
  • [n/a] NVIDIA container library logs (see troubleshooting)
  • [point 2.] Docker command, image and tag used
@elezar
Copy link
Member

elezar commented Apr 12, 2023

@Overcraft90 this would be an issue to raise with the maintainers of the deep-variant image and is not related to the NVIDIA container stack.

Have you asked whether they would be able to bump their base images?

@Overcraft90
Copy link
Author

@elezar thanks for the suggestion, I haven't but I will definitely move on and do so. In the meantime, Can I keep this issue open till I will have an answer from their side? Thanks!

@elezar
Copy link
Member

elezar commented Apr 13, 2023

Sure let's keep it open.

@elezar
Copy link
Member

elezar commented Nov 19, 2023

@Overcraft90 I am closing this issue now.

For more details on the current image support policy see:

The lifetime of images is out of scope for this project, so please consider opening an issue there instead.

@elezar elezar closed this as completed Nov 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants