-
Bug
-
Resolution: Done
-
Undefined
-
rhelai-1.4
-
False
-
-
False
-
-
-
AIPCC Application Platform 4
To Reproduce Steps to reproduce the behavior:
- Install Intel Gaudi image
- cat /usr/bin/ilab
- code to import local env variables is missing, can be compared with ilab wrapper from Nvidia image
Expected behavior
- ilab wrapper to consider local env variables as done in Nvidia image
Screenshots
- Attached Image
Device Info (please complete the following information):
- Hardware Specs: Any
- OS Version: Rhel AI 1.4 Intel Gaudi
- InstructLab Version: [ilab, version 0.23.1]
- Provide the output of these two commands:
- registry.stage.redhat.io/rhelai1/bootc-intel-rhel9:1.4
- ...
InstructLab:
instructlab.version: 0.23.1
instructlab-dolomite.version: 0.2.0
instructlab-eval.version: 0.5.1
instructlab-quantize.version: 0.1.0
instructlab-schema.version: 0.4.2
instructlab-sdg.version: 0.7.0
instructlab-training.version: 0.7.0
Torch:
torch.version: 2.5.1a0+git6fc067b
torch.backends.cpu.capability: AVX512
torch.version.cuda: None
torch.version.hip: None
torch.cuda.available: False
torch.backends.cuda.is_built: False
torch.backends.mps.is_built: False
torch.backends.mps.is_available: False
habana_torch_plugin.version: 1.19.1.26
torch.hpu.is_available: True
torch.hpu.device_count: 8
...
Bug impact
- It is easy for customers to import local variable that can be used with podman command in ilab wrapper, if needed. Otherwise, they have to copy ilab wrapper and update the code or, need to unlock the filesystem & edit the ilab wrapper. Consider
RHELAI-3528as a scenario
Known workaround
- Enable modifications to filesystem by running a[sudo rpm-ostree usroverlay] and modify ilab wrapper. This will not persist on reboot
- create a copy of the wrapper [/bin/ilab] in home directory , edit it, and run from there
Additional context
- Code from Nvidia image
# If you need to set additional environment variables into the container, you can specify them # using the ILAB_ADDITIONAL_ENV environment variable. # # Example ILAB_ADDITIONAL_ENV usage: # # export VAR_A="some text" # export ILAB_ADDITIONAL_ENV="VAR_A VAR_B=someothertext VAR_C='text with spaces'" ADDITIONAL_ENV=() if [ -n "${ILAB_ADDITIONAL_ENV}" ]; then # (eval is used here to allow the user to specify mounts that might have spaces in them) eval "ADDITIONAL_ENV=(${ILAB_ADDITIONAL_ENV})" fi ADDITIONAL_ENV_VARS=() for ENV_VAR in "${ADDITIONAL_ENV[@]}"; do ADDITIONAL_ENV_VARS+=("--env" "$ENV_VAR") done PODMAN_COMMAND=("podman" "run" "--rm" "-it" "--device" "${CONTAINER_DEVICE}" "--security-opt" "label=disable" "--net" "host" "--shm-size" "10G" "--pids-limit" "-1" "-v" "$HOME:$HOME" "${ADDITIONAL_MOUNT_OPTIONS[@]}" "${ADDITIONAL_ENV_VARS[@]}" "--env" "HF_TOKEN" "--env" "HOME" "--env" "NCCL_DEBUG" "--env" "VLLM_LOGGING_LEVEL" "--entrypoint" "$ENTRYPOINT" "${IMAGE_NAME}")