Error when sharing environment from workspace to registry #39502
Labels
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Machine Learning
needs-team-attention
Workflow: This issue needs attention from Azure service team or SDK team
Service Attention
Workflow: This issue is responsible by Azure service team.
azure-ai-ml
1.23.0
3.11.11
Describe the bug
We are trying to use the AML Registry to share components across workspaces. As indicated in the documentation for a secure AML Registry, we must build the environment in the workspace before we share it to the AML Registry.
When we try to onboard different components that share the same environment concurrently, this often results in:
To wait until the environment was built, we rely on an error message raised by the AML Registry, as there is no way to wait for the environment build to complete in the v2 SDK. Is there another way how we can make sharing components in an AML Registry work when using the v2 SDK? We cannot publish the components directly to the AML Registry due to the bug reported here.
To Reproduce
I used the following script to reproduce the issue, and for me it consistently occurs after one or two tries. Make sure that the
requirements.txt
is modified between runs to avoid caching of an already built environment/image.With the following build context:
Dockerfile:
requirements.txt:
We share a global client instance as
MLClient
was indicated to be immutable.The full error is as follows:
Steps to reproduce the behavior:
Expected behavior
All environments should be successfully published to the AML Registry after a while.
The text was updated successfully, but these errors were encountered: