Skip to content

Commit 1bfd599

Browse files
authored
add zstd to framework container (#1363)
See if we can fix broken CI builds with zstd Signed-off-by: Peter St. John <pstjohn@nvidia.com>
1 parent efda3a5 commit 1bfd599

1 file changed

Lines changed: 3 additions & 4 deletions

File tree

Dockerfile

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -228,15 +228,14 @@ uv pip install --no-build-isolation \
228228
-r /requirements-test.txt
229229

230230
# Install back ngcsdk, as a WAR for the protobuf version conflict with nemo_toolkit.
231-
uv pip install ngcsdk==3.64.3 # Temporary fix for changed filename, see https://nvidia.slack.com/archives/C074Z808N05/p1746231345981209
231+
uv pip install ngcsdk==4.9.17 # latest version, 12/03/2025.
232232
# Install >=0.46.1 bitsandbytes specifically because it has CUDA>12.9 support.
233233
# TODO(trvachov) remove this once it stops conflicting with strange NeMo requirements.txt files
234234
uv pip uninstall bitsandbytes && uv pip install bitsandbytes==0.46.1
235235

236236
# Addressing security scan issue - CVE vulnerability https://github.com/advisories/GHSA-g4r7-86gm-pgqc The package is a
237-
# dependency of lm_eval from NeMo requirements_eval.txt. We also remove zstandard, another dependency of lm_eval, which
238-
# seems to be causing issues with NGC downloads. See https://nvbugspro.nvidia.com/bug/5149698
239-
uv pip uninstall sqlitedict zstandard
237+
# dependency of lm_eval from NeMo requirements_eval.txt.
238+
uv pip uninstall sqlitedict
240239

241240
rm -rf ./3rdparty
242241
rm -rf /tmp/*

0 commit comments

Comments
 (0)