NVIDIA
NVIDIA
BioNeMo Framework
Container
NVIDIA
NVIDIA
BioNeMo Framework

BioNeMo Framework for running training and inference on large scale bio-based models.

LayerLabelCreated
sha256:f30ab5c29837b06755572f45d7bd3596800f757113a62b566eb4522f98dcfcdeRUN
chmod 777 -R /workspace/bionemo2/
10/28/2025 5:27 PM UTC
sha256:f7db59f9a45b98830fe16222e108e6c47bbb08d66082fa22ed77ea9c2a805f76RUN
uv pip install h11==0.16.0
10/28/2025 5:27 PM UTC
sha256:6b51d94a5de5e04f5a3eb7a1b07dd10aa9687fd8dc25d5fc5e987418b2eef145COPY
/usr/local/rustup /usr/local/rustup
10/28/2025 5:27 PM UTC
sha256:73fbe2d4b53a3219720c5a929ebe415d5b3aa784478e38c457dd5de5e5792659COPY
/usr/local/cargo /usr/local/cargo
10/28/2025 5:27 PM UTC
sha256:d856e19b7c1404116831e5940b046589f82628c8dc9f4a6a40d602bd9cbf1182COPY
./docs ./docs
10/28/2025 5:27 PM UTC
sha256:79fa448bba3ba2a5fa8d79c84295f6fb72a1d153f9a516e92b4c08cc490a191dCOPY
./ci/scripts ./ci/scripts
10/28/2025 5:27 PM UTC
sha256:4e85dca8014d272be3135eea56597c144233383ed849e0997ee8c741e6c6bc20COPY
./README.md ./
10/28/2025 5:27 PM UTC
sha256:58dd976c2898848fd83d92df16ad51d231a36f414e7aaf2fac206ebac55e80fdCOPY
VERSION .
10/28/2025 5:27 PM UTC
sha256:f8326f00b602df634f33b8251ba5c9435d69afe7150dce619f4c7828e5c5b043RUN
mkdir -p /workspace/bionemo2/.cache/
10/23/2025 2:54 AM UTC
sha256:016af0646fa70dccc4e207f9d17e91accbde295722ad822b6cd71d09fe5afe4bRUN
RUN |4 TARGETARCH=amd64 TE_TAG=9d4e11eaa508383e35b510dc338e58b09c30be73 CAUSAL_CONV_TAG=52e06e3d5ca10af0c7eb94a520d768c48ef36f1f NEMU_RUN_TAG=v0.3.0 /bin/sh -c set -eo pipefail uv pip install maturin --no-build-isolation # install nvidia-resiliency-ext separately because it doesn't yet have ARM wheels
git clone https://github.com/NVIDIA/nvidia-resiliency-ext
uv pip install nvidia-resiliency-ext/
rm -rf nvidia-resiliency-ext/
# ngcsdk causes strange dependency conflicts (ngcsdk requires protobuf<4, but nemo_toolkit requires protobuf==4.24.4, deleting it from the uv pip install prevents installation conflicts)
sed -i "/ngcsdk/d" ./sub-packages/bionemo-core/pyproject.toml
# Remove llama-index because bionemo doesn't use it and it adds CVEs to container sed -i "/llama-index/d" ./3rdparty/NeMo/requirements/requirements_nlp.txt # Pin 'nvidia-modelopt' to 0.27.1 due to an API incompatibility of version 0.25.0 sed -i -E "s|nvidia-modelopt\[torch\]>=[^,]+,<=([^ ;]+)|nvidia-modelopt[torch]==\1|" ./3rdparty/NeMo/requirements/requirements_nlp.txt uv pip install --no-build-isolation \
./3rdparty/* \
./sub-packages/bionemo-* \
-r /requirements-cve.txt \
-r /requirements-test.txt # Install back ngcsdk, as a WAR for the protobuf version conflict with nemo_toolkit. uv pip install ngcsdk==3.64.3 # Temporary fix for changed filename, see https://nvidia.slack.com/archives/C074Z808N05/p1746231345981209 # Install >=0.46.1 bitsandbytes specifically because it has CUDA>12.9 support. # TODO(trvachov) remove this once it stops conflicting with strange NeMo requirements.txt files uv pip uninstall bitsandbytes && uv pip install bitsandbytes==0.46.1 # Addressing security scan issue - CVE vulnerability https://github.com/advisories/GHSA-g4r7-86gm-pgqc The package is a # dependency of lm_eval from NeMo requirements_eval.txt. We also remove zstandard, another dependency of lm_eval, which # seems to be causing issues with NGC downloads. See https://nvbugspro.nvidia.com/bug/5149698 uv pip uninstall sqlitedict zstandard rm -rf ./3rdparty rm -rf /tmp/* rm -rf ./sub-packages/bionemo-noodles/target # buildkit
10/23/2025 2:54 AM UTC
...

NVIDIA uses cookies to improve your experience on our web site. We and our third-party partners also use cookies and other tools to collect and record information you provide as well as information about your interactions with our websites for performance improvement, analytics, and to assist in marketing efforts. By clicking "Accept All", you consent to our use of cookies and other tools as described in our Cookie Policy. You can manage your cookie settings by clicking on "Manage Settings." By continuing to use this site or by clicking one of the buttons below, you agree to our Terms of Service (which contains important waivers). Please see our Privacy Policy for more information on our privacy practices.