Skip to content

Raghu/baseimage update#4134

Closed
raghu-microsoft wants to merge 8 commits into
mainfrom
raghu/baseimage_update
Closed

Raghu/baseimage update#4134
raghu-microsoft wants to merge 8 commits into
mainfrom
raghu/baseimage_update

Conversation

@raghu-microsoft
Copy link
Copy Markdown
Contributor

image
Tested locally It is working,

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 30, 2025

Test Results for assets-test

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 5a4ddaa.

♻️ This comment has been updated with latest results.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 30, 2025

Test Results for training-model-mgmt-unittests

29 tests   28 ✅  7s ⏱️
 1 suites   0 💤
 1 files     1 ❌

For more details on these failures, see this check.

Results for commit 5a4ddaa.

♻️ This comment has been updated with latest results.


code: ../../src/
command: |
pip install transformers==4.48.0 torch==2.2.2 numpy==1.23.5 pandas==1.5.3 urllib3==1.26.19 --no-cache-dir --force-reinstall
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

runtime dependencies installation? sweet...

Copy link
Copy Markdown
Contributor Author

@raghu-microsoft raghu-microsoft May 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I initially tried moving dependencies into requirements.txt, but ran into an issue:
[module 'azureml.evaluate.mlflow' has no attribute 'hftransformers']
This happens because the required transformers and compatible torch versions aren’t guaranteed to be installed or active early enough in the environment lifecycle.
To ensure compatibility and avoid evaluation failures, I opted to install the runtime dependencies explicitly in the spec.yaml. This guarantees they’re available at execution time, avoiding any cached or conflicting versions.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I incorporated the required libraries directly into the Dockerfile rather than using the spec.yaml file.
After adding those changes, I ran import_model, it is now running successfully.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vizhur, Could you please review this PR

Included the necessary libraries directly in the Dockerfile instead of using the spec.yaml file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants