Skip to content

Commit b4aaf7d

Browse files
Merge pull request #230484 from lykelly19/patch-4
Update public docs for Unknown Docker commands not caught, file not found in Docker context, and not a git repository failure scenarios
2 parents 4eaef4a + c082d68 commit b4aaf7d

File tree

1 file changed

+66
-0
lines changed

1 file changed

+66
-0
lines changed

articles/machine-learning/how-to-troubleshoot-environments.md

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1197,6 +1197,25 @@ az ml workspace update --name myworkspace --resource-group myresourcegroup --ima
11971197
* [Enable Azure Container Registry (ACR)](https://aka.ms/azureml/environment/acr-private-endpoint)
11981198
* [How To Use Environments](https://aka.ms/azureml/environment/how-to-use-environments)
11991199

1200+
### Unexpected Dockerfile Format
1201+
<!--issueDescription-->
1202+
This issue can happen when your Dockerfile is formatted incorrectly.
1203+
1204+
**Potential causes:**
1205+
* Your Dockerfile contains invalid syntax
1206+
* Your Dockerfile contains characters that aren't compatible with UTF-8
1207+
1208+
**Affected areas (symptoms):**
1209+
* Failure in building environments from UI, SDK, and CLI.
1210+
* Failure in running jobs because it will implicitly build the environment in the first step.
1211+
<!--/issueDescription-->
1212+
1213+
**Troubleshooting steps**
1214+
* Ensure Dockerfile is formatted correctly and is encoded in UTF-8
1215+
1216+
**Resources**
1217+
* [Dockerfile format](https://docs.docker.com/engine/reference/builder/#format)
1218+
12001219
## *Docker pull issues*
12011220
### Failed to pull Docker image
12021221
<!--issueDescription-->
@@ -1731,6 +1750,7 @@ This issue can happen when you haven't specified any targets and no makefile is
17311750
**Affected areas (symptoms):**
17321751
* Failure in building environments from UI, SDK, and CLI.
17331752
* Failure in running jobs because Azure Machine Learning implicitly builds the environment in the first step.
1753+
<!--/issueDescription-->
17341754
17351755
**Troubleshooting steps**
17361756
* Ensure that you've spelled the makefile correctly
@@ -1742,8 +1762,31 @@ This issue can happen when you haven't specified any targets and no makefile is
17421762
17431763
**Resources**
17441764
* [GNU Make](https://www.gnu.org/software/make/manual/make.html)
1765+
1766+
## *Copy issues*
1767+
### File not found
1768+
<!--issueDescription-->
1769+
This issue can happen when Docker fails to find and copy a file.
1770+
1771+
**Potential causes:**
1772+
* Source file not found in Docker build context
1773+
* Source file excluded by `.dockerignore`
1774+
1775+
**Affected areas (symptoms):**
1776+
* Failure in building environments from UI, SDK, and CLI.
1777+
* Failure in running jobs because it will implicitly build the environment in the first step.
17451778
<!--/issueDescription-->
17461779
1780+
**Troubleshooting steps**
1781+
* Ensure that the source file exists in the Docker build context
1782+
* Ensure that the source and destination paths exist and are spelled correctly
1783+
* Ensure that the source file isn't listed in the `.dockerignore` of the current and parent directories
1784+
* Remove any trailing comments from the same line as the `COPY` command
1785+
1786+
**Resources**
1787+
* [Docker COPY](https://docs.docker.com/engine/reference/builder/#copy)
1788+
* [Docker Build Context](https://docs.docker.com/engine/context/working-with-contexts/)
1789+
17471790
## *Docker push issues*
17481791
### Failed to store Docker image
17491792
<!--issueDescription-->
@@ -1772,6 +1815,29 @@ If you aren't using a virtual network, or if you've configured it correctly, tes
17721815
* For an image "helloworld", test pushing to your ACR by running `docker push helloworld`
17731816
* See [Quickstart: Build and run a container image using Azure Container Registry Tasks](../container-registry/container-registry-quickstart-task-cli.md)
17741817
1818+
## *Unknown Docker command*
1819+
### Unknown Docker instruction
1820+
<!--issueDescription-->
1821+
This issue can happen when Docker doesn't recognize an instruction in the Dockerfile.
1822+
1823+
**Potential causes:**
1824+
* Unknown Docker instruction being used in Dockerfile
1825+
* Your Dockerfile contains invalid syntax
1826+
1827+
**Affected areas (symptoms):**
1828+
* Failure in building environments from UI, SDK, and CLI.
1829+
* Failure in running jobs because it will implicitly build the environment in the first step.
1830+
<!--/issueDescription-->
1831+
1832+
**Troubleshooting steps**
1833+
* Ensure that the Docker command is valid and spelled correctly
1834+
* Ensure there's a space between the Docker command and arguments
1835+
* Ensure there's no unnecessary whitespace in the Dockerfile
1836+
* Ensure Dockerfile is formatted correctly and is encoded in UTF-8
1837+
1838+
**Resources**
1839+
* [Dockerfile reference](https://docs.docker.com/engine/reference/builder/)
1840+
17751841
## *Miscellaneous build issues*
17761842
### Build log unavailable
17771843
<!--issueDescription-->

0 commit comments

Comments
 (0)