Clara Parabricks 4 on Hopper

Could it be possible to run parabricks/4 on H100 gpu? I tried to run docker image, and failed. Since I didn’t see Hopper was mentioned in the doc, I’m wondering if there is some hardware restriction before spending more time troubleshooting it.

docker run --gpus all --mount type=bind,source=/yuq3/parabricks,target=/parab -it /usr/bin/bash

pbrun fq2bam       --ref ./parabricks_sample/Ref/Homo_sapiens_assembly38.fasta       --in-fq ./parabricks_sample/Data/sample_1.fq.gz ./parabricks_sample/Data/sample_2.fq.gz       --out-bam fq2bam_output.bam
Please visit for detailed documentation

[Parabricks Options Mesg]: Checking argument compatibility
[Parabricks Options Mesg]: Automatically generating ID prefix
[Parabricks Options Mesg]: Read group created for /parab/parabricks_sample/Data/sample_1.fq.gz and
[Parabricks Options Mesg]: @RG\tID:HK3TJBCX2.1\tLB:lib1\tPL:bar\tSM:sample\tPU:HK3TJBCX2.1
[PB Info 2023-Mar-17 17:19:43] ------------------------------------------------------------------------------
[PB Info 2023-Mar-17 17:19:43] ||                 Parabricks accelerated Genomics Pipeline                 ||
[PB Info 2023-Mar-17 17:19:43] ||                              Version 4.0.1-1                             ||
[PB Info 2023-Mar-17 17:19:43] ||                       GPU-BWA mem, Sorting Phase-I                       ||
[PB Info 2023-Mar-17 17:19:43] ------------------------------------------------------------------------------
[M::bwa_idx_load_from_disk] read 0 ALT contigs
[PB Info 2023-Mar-17 17:19:49] GPU-BWA mem
[PB Info 2023-Mar-17 17:19:49] ProgressMeter    Reads           Base Pairs Aligned
[PB Warning 2023-Mar-17 17:19:51][ParaBricks/src/] cudaSafeCall() failed at ParaBricks/src/ invalid device symbol
[PB Error 2023-Mar-17 17:19:51][ParaBricks/src/] No GPUs active, shutting down due to previous error., exiting.
For technical support visit

Could not run fq2bam
Exiting pbrun ...

You are correct. Hopper support is coming in the next version of Parabricks.