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
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-troubleshoot-environments.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ Environment isolation implies that Python dependencies installed in the base ima
42
42
43
43
### Create and manage environments
44
44
45
-
You can create and manage environments from clients like AzureML Python SDK, AzureML CLI, AzureML Studio UI, VS code extension.
45
+
You can create and manage environments from clients like AzureML Python SDK, AzureML CLI, AzureML Studio UI, Visual Studio Code extension.
46
46
47
47
"Anonymous" environments are automatically registered in your workspace when you submit an experiment without registering or referencing an already existing environment.
48
48
They aren't listed but you can retrieve them by version or label.
@@ -68,7 +68,7 @@ There are some ways to decrease the impact of vulnerabilities:
68
68
69
69
#### *Vulnerabilities vs Reproducibility*
70
70
71
-
Reproducibility is one of the foundations of software development. While developing production code, a repeated operation must guarantee the same
71
+
Reproducibility is one of the foundations of software development. When you're developing production code, a repeated operation must guarantee the same
72
72
result. Mitigating vulnerabilities can disrupt reproducibility by changing dependencies.
73
73
74
74
AzureML's primary focus is to guarantee reproducibility. Environments fall under three categories: curated,
@@ -1141,7 +1141,7 @@ See the [samples repository](https://aka.ms/azureml/environment/train-r-models-c
1141
1141
1142
1142
**Troubleshooting steps**
1143
1143
1144
-
Ensure that you are specifying your environment name correctly, along with the correct version
1144
+
Ensure that you're specifying your environment name correctly, along with the correct version
1145
1145
* `path-to-resource:version-number`
1146
1146
1147
1147
You should specify the 'latest' version of your environment in a different way
@@ -1233,7 +1233,7 @@ This issue can happen when a Docker image pull fails due to a network issue.
1233
1233
**Potential causes:**
1234
1234
* Network connection issue, which could be temporary
1235
1235
* Firewall is blocking the connection
1236
-
* ACR is unreachable and there's network isolation. For more details, see [ACR unreachable](#acr-unreachable).
1236
+
* ACR is unreachable and there's network isolation. For more information, see [ACR unreachable](#acr-unreachable).
1237
1237
1238
1238
**Affected areas (symptoms):**
1239
1239
* Failure in building environments from UI, SDK, and CLI.
@@ -1640,7 +1640,7 @@ Alternatively, use a different version of Python that's compatible with the pack
1640
1640
1641
1641
### Conda bare redirection
1642
1642
<!--issueDescription-->
1643
-
This issue can happen when a package is specified on the command line using "<" or ">" without using quotes, causing conda environment creation or update to fail.
1643
+
This issue can happen when you've specified a package on the command line using "<" or ">" without using quotes, which can cause conda environment creation or update to fail.
1644
1644
1645
1645
**Affected areas (symptoms):**
1646
1646
* Failure in building environments from UI, SDK, and CLI.
@@ -1671,7 +1671,7 @@ This issue can happen when your image build fails during Python package installa
1671
1671
1672
1672
**Potential causes:**
1673
1673
* There are many issues that could cause this error
1674
-
* This is a generic message that's surfaced when the error you're encountering isn't yet covered by AzureML analysis
1674
+
* This message is generic and is surfaced when AzureML analysis doesn't yet cover the error you're encountering
1675
1675
1676
1676
**Affected areas (symptoms):**
1677
1677
* Failure in building environments from UI, SDK, and CLI.
@@ -1687,7 +1687,7 @@ Leave feedback for the AzureML team to analyze the error you're experiencing
1687
1687
1688
1688
### Can't uninstall package
1689
1689
<!--issueDescription-->
1690
-
This can happen when pip fails to uninstall a Python package that was installed via the operating system's package manager.
1690
+
This issue can happen when pip fails to uninstall a Python package that the operating system's package manager installed.
1691
1691
1692
1692
**Potential causes:**
1693
1693
* An existing pip problem or a problematic pip version
@@ -1700,8 +1700,8 @@ This can happen when pip fails to uninstall a Python package that was installed
1700
1700
1701
1701
**Troubleshooting steps**
1702
1702
1703
-
Read the following and determine if your failure is caused by an existing pip problem
1704
-
* [Cannot uninstall while creating Docker image](https://stackoverflow.com/questions/63383400/error-cannot-uninstall-ruamel-yaml-while-creating-docker-image-for-azure-ml-a)
1703
+
Read the following and determine if an existing pip problem caused your failure
1704
+
* [Can't uninstall while creating Docker image](https://stackoverflow.com/questions/63383400/error-cannot-uninstall-ruamel-yaml-while-creating-docker-image-for-azure-ml-a)
@@ -1741,7 +1741,7 @@ This issue can happen when no targets are specified and no makefile is found whe
1741
1741
## *Docker push issues*
1742
1742
### Failed to store Docker image
1743
1743
<!--issueDescription-->
1744
-
This issue can happen when a Docker image fails to be stored (pushed) to a container registry.
1744
+
This issue can happen when a Docker image push to a container registry fails.
1745
1745
1746
1746
**Potential causes:**
1747
1747
* A transient issue has occurred with the ACR associated with the workspace
@@ -1754,7 +1754,7 @@ This issue can happen when a Docker image fails to be stored (pushed) to a conta
1754
1754
1755
1755
**Troubleshooting steps**
1756
1756
1757
-
Retry the environment build if you suspect this is a transient issue with the workspace's Azure Container Registry (ACR)
1757
+
Retry the environment build if you suspect the failure is a transient issue with the workspace's Azure Container Registry (ACR)
1758
1758
1759
1759
If your container registry is behind a virtual network or is using a private endpoint in an [unsupported region](https://aka.ms/azureml/environment/private-link-availability)
1760
1760
* Configure the container registry by using the service endpoint (public access) from the portal and retry
0 commit comments