Can't access image build failure logs for AML Registry environments

[bastbu]

• Package Name: azure-ai-ml
• Package Version: 1.23.0
• Operating System: Ubuntu
• Python Version: 3.11.11

Describe the bug

When publishing a failing environment to the AML Registry, it would be useful to have access to the build failure logs to troubleshoot failing image builds. The error message I get is as follows:

azure.core.exceptions.HttpResponseError: (UserError) Image build failed. Build log: https://weumanaged209.blob.core.windows.net/8531a207eaa442f1b0cc192d761b9f02-2xwetlstb5/logs/cba3/rawtext.log
Code: UserError
Message: Image build failed. Build log: https://weumanaged209.blob.core.windows.net/8531a207eaa442f1b0cc192d761b9f02-2xwetlstb5/logs/cba3/rawtext.log

When I try to access the build log, I get the following error:

ERROR 409: Public access is not permitted on this storage account..

What is the recommended way to access the build failure logs with the AML SDK?

To Reproduce

Steps to reproduce the behavior:

1. Create an environment with an error in the Docker build context, i.e. using:

from pathlib import Path

from azure.ai.ml import MLClient
from azure.ai.ml.entities import BuildContext, Environment


def main(ml_client: MLClient):
    _ = ml_client.environments.create_or_update(
        Environment(
            build=BuildContext(
                path=Path(__file__).parent / "environment",
            )
        )
    )

I used the following Dockerfile to provoke an error:

some_error

Expected behavior

The error message should contain enough information to allow me to debug the failing image build.

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-ml-sdk @azureml-github.

[achauhan-scc]

@bastbu - I am assuming you are getting error while creating an environment in registry?

[bastbu]

@bastbu - I am assuming you are getting error while creating an environment in registry?

@achauhan-scc Exactly, the MLClient that I inject is configured to point towards a registry.

[achauhan-scc]

@bastbu - registry build logs are unavailable through our system. But registry owner should have access to the ACR task logs (for relatively short period of time)