The goal of this guide is to walk through the steps to create a custom GPU instance on NVIDIA Brev using the Brev Launchable interface.
Brev provides access to a wide variety of GPU instances on difference cloud environment. While this provides you flexibility on pricing and avaiablity, it makes it difficult to test this launchable on every combination of compute environment and cloud environment. As such, some tinkering may be required to get the instance to work on the specific configuration you select. To use one of our recommended environments that is tested to work, please check out the Quickstart Instructions.
Warning
Our Docker Compose YAML files have a known issue when using GCP resources on Brev. We recommend using another cloud provider until this is resolved.
- Go to Brev’s Launchable Creator (requires account)
- When asked How would you like to provide your code files? select "I have code files in a GitHub repository". Enter the URL of this repository.
- When asked What type of runtime environment do you need? select "With container(s)"
- Under Choose a Container Configuration select "Docker Compose" and click on the toggle to select "I have an existing docker-compose.yaml file".
- Under Upload Docker Compose select "Provide GitHub/Gitlab URL" and provide a link to one of the Docker Compose YAML files in the docker/brev directory. There is a README.md in that directory with instructions on which YAML to select. Please take note that Blackwell GPUs require CUDA13 while other GPU instances usually will work on CUDA12. Note, you need to pass a link to the file in GitHub, not to the
raw.github.comfile (e.g. docker-compose-nb-2602-cuda13.yaml). Click "Validate". - On the next page, when asked Do you want a Jupyter Notebook experience? select "No, I don't want Jupyter (Not Recommended)". We will provide Jupyter in the Docker compose already.
- In the section title Do you need to expose services? make sure that ports
8888,8787, and8786are open. Name port 8888jupyterso Brev can treat it as a jupyterlab based instance and provide an Open Notebook button. - Select your desired compute environment. Make sure you select sufficient disk size to download the datasets you want to work with. We recommend at least 128GB, unless you want to run the 11M cell notebook, which you will need atleast 200GB. Note, you will not be able to resize the instance once created.
- Create a name for your launchable, and deploy.
Note
Git is not installed by default in this container, but it can be installed using
apt update
apt install git -y
A second option to set up rapids-singlecell is to start by Creating a Custom RAPIDS Brev Instance, manually git cloning this single-cell-analysis-blueprint repository, and manually installing the scverse rapids-singlecell library.
- Follow the instructions for Creating a RAPIDS Brev Instance. Remember the RAPIDS version for Step 3. Launch the instance.
- Download this repository into the instance.
- Download the
rapids-singlecellrepository into the instance. Follow their installation instructions. It is important to have the same RAPIDS version and CUDA Toolkit version as your installed RAPIDS versions. For Brev, we currently default to CUDA Toolkit 13 to support Blackwell GPUs and CUDA Toolkit 12 for other GPUs. Therefore, you can installrapids-singelcellusing `mamba env create -f conda/rsc_.yml'- Example to install
rapids-singelcellfor 26.02
mamba env create -f conda/rsc_rapids_26.02.yml - Example to install
You can check this by going to the command line and running nvcc --version inside the instance. You'll get an output like this:
```bash
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2025 NVIDIA Corporation
Built on Fri_Feb_21_20:26:18_PST_2025
Cuda compilation tools, release 12.8, V12.8.93
Build cuda_12.8.r12.8/compiler.35583870_0
```
- Activate the mamba environment and run the notebooks/your code.
mamba activate rapids-singelcell