From 3f6afc6f191ab78309851cc8749076ac9d382831 Mon Sep 17 00:00:00 2001 From: Chuck Lantz Date: Wed, 3 Apr 2019 15:42:40 -0700 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 701fd9bf3b..d78b922184 100644 --- a/README.md +++ b/README.md @@ -53,7 +53,7 @@ Check out the `container-templates` folder for simple examples and the definitio #### Are development containers intended to define how an application is deployed? -No. A development container is an environment that you can use to develop your application even before you are ready to build or deploy. The "dev container definitions" found in the [vscode-dev-containers repo](https://aka.ms/vscode-dev-containers) are intended to help jump start this process by including a set of well-known container build or deployment files and a `devcontainer.json` file. `devcontainer.json` is not intended to provide a home for tooling and edit-time related settings and a pointer to the image (or files that define the image) that should be used for the development container. +No. A development container is an environment that you can use to develop your application even before you are ready to build or deploy. The "dev container definitions" found in the [vscode-dev-containers repo](https://aka.ms/vscode-dev-containers) are intended to help jump start this process by including a set of well-known container build or deployment files and a `devcontainer.json` file. This file provides a home for tooling and edit-time related settings and a pointer to the image (or files that define the image) that should be used for the development container. Support for [attaching to a running container](#attaching-to-running-containers) can be used to interact with deployment focused containers or for other container build or deployment workflows.