Skip to content

Commit fccab37

Browse files
authored
Update how-to-manage-environments-v2.md
1 parent a8a4e0f commit fccab37

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

articles/machine-learning/how-to-manage-environments-v2.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -136,9 +136,6 @@ ml_client.environments.create_or_update(env_docker_image)
136136

137137
Instead of defining an environment from a prebuilt image, you can also define one from a Docker [build context](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#understand-build-context). To do so, specify the directory that will serve as the build context. This directory should contain a Dockerfile (not larger than 1MB) and any other files needed to build the image.
138138

139-
> [!NOTE]
140-
> Uploading a Dockerfile larger than 1MB is currently unsupported.
141-
142139
# [Azure CLI](#tab/cli)
143140

144141
The following example is a YAML specification file for an environment defined from a build context. The local path to the build context folder is specified in the `build.path` field, and the relative path to the Dockerfile within that build context folder is specified in the `build.dockerfile_path` field. If `build.dockerfile_path` is omitted in the YAML file, Azure Machine Learning will look for a Dockerfile named `Dockerfile` at the root of the build context.

0 commit comments

Comments
 (0)