You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cd examples/digital_fingerprinting/production
export MORPHEUS_CONTAINER_VERSION="$(git describe --tags --abbrev=0)-runtime"
docker compose build
docker compose up jupyter
Relevant log output
Click here to see error details
[jupyter base 3/5] RUN source activate morpheus && mamba env update -n morpheus --file /workspace/conda/environments/examples_cuda-121_arch-x86_64.yaml:
2.114 Channels:
2.114 - conda-forge
2.114 - huggingface
2.114 - rapidsai
2.114 - rapidsai-nightly
2.114 - nvidia
2.114 - nvidia/label/dev
2.114 - pytorch
2.114 - local
2.114 Platform: linux-64
2.114 Collecting package metadata (repodata.json): ...working... failed
6.973
6.973 UnavailableInvalidChannel: HTTP 404 UNAVAILABLE OR INVALID for channel opt/conda/conda-bld file:///opt/conda/conda-bld
6.973
6.973 The channel is not accessible or is invalid.
6.973
6.973 You will need to adjust your conda configuration to proceed.
6.973 Use conda config --show channels to view your configuration's current state,
6.973 and use conda config --show-sources to view config file locations.
6.973
6.973 As of conda 4.3, a valid channel must contain a noarch/repodata.json and
6.973 associated noarch/repodata.json.bz2 file, even if noarch/repodata.json is
6.973 empty. Use conda index /opt/conda/conda-bld, or create noarch/repodata.json
6.973 and associated noarch/repodata.json.bz2.
6.973
6.973
[+] Running 1/1
! jupyter Warning pull access denied for dfp_morpheus_jupyter, repository does not exist or may require 'docker login': denied: requested access to the resour... 1.1s
[+] Building 7.1s (7/10) docker:default
=> [jupyter internal] load build definition from Dockerfile 0.1s
=> => transferring dockerfile: 2.38kB 0.0s
=> [jupyter internal] load .dockerignore 0.1s
=> => transferring context: 213B 0.0s
=> [jupyter internal] load metadata for nvcr.io/nvidia/morpheus/morpheus:v24.06.00rc1-runtime 0.0s
=> [jupyter base 1/5] FROM nvcr.io/nvidia/morpheus/morpheus:v24.06.00rc1-runtime 0.0s
=> [jupyter internal] load build context 0.1s
=> => transferring context: 12.58kB 0.0s
=> CACHED [jupyter base 2/5] WORKDIR /workspace/examples/digital_fingerprinting/ 0.0s
=> ERROR [jupyter base 3/5] RUN source activate morpheus && mamba env update -n morpheus --file /workspace/conda/environments/examples_cuda-121_arch-x86_64.yaml 7.0s
[jupyter base 3/5] RUN source activate morpheus && mamba env update -n morpheus --file /workspace/conda/environments/examples_cuda-121_arch-x86_64.yaml:
1.770 Channels:
1.770 - conda-forge
1.770 - huggingface
1.770 - rapidsai
1.770 - rapidsai-nightly
1.770 - nvidia
1.770 - nvidia/label/dev
1.770 - pytorch
1.770 - local
1.770 Platform: linux-64
1.770 Collecting package metadata (repodata.json): ...working... failed
6.632
6.632 UnavailableInvalidChannel: HTTP 404 UNAVAILABLE OR INVALID for channel opt/conda/conda-bld file:///opt/conda/conda-bld
6.632
6.632 The channel is not accessible or is invalid.
6.632
6.632 You will need to adjust your conda configuration to proceed.
6.632 Use conda config --show channels to view your configuration's current state,
6.632 and use conda config --show-sources to view config file locations.
6.632
6.632 As of conda 4.3, a valid channel must contain a noarch/repodata.json and
6.632 associated noarch/repodata.json.bz2 file, even if noarch/repodata.json is
6.632 empty. Use conda index /opt/conda/conda-bld, or create noarch/repodata.json
6.632 and associated noarch/repodata.json.bz2.
6.632
6.632
Version
24.06
Which installation method(s) does this occur on?
Source
Describe the bug.
failed to solve: executor failed running [/bin/bash -c source activate morpheus && mamba env update -n morpheus --file /workspace/conda/environments/examples_cuda-121_arch-x86_64.yaml]: exit code: 1
Minimum reproducible example
Relevant log output
Click here to see error details
Full env printout
Click here to see environment details
Other/Misc.
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: