Skip to content
This repository has been archived by the owner on Nov 30, 2023. It is now read-only.

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Chuxel committed Aug 7, 2019
1 parent bd042c2 commit c666128
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@

A **development container** is a running [Docker](https://www.docker.com) container with a well-defined tool/runtime stack and its prerequisites. The Remote - Containers extension in the [Remote Development](https://aka.ms/vscode-remote/download/extension) extension pack allows you to open any folder mounted into or inside a dev container and take advantage of VS Code's full development feature set.

This repository contains a set of **dev container definitions** to help get you up and running with a containerized environment. The definitions describe the appropriate container image, runtime arguments for starting the container, and VS Code extensions that should be installed. They provide files beyond the `devcontainer.json` container configuration file like Dockerfiles or Docker Compose files that they can be dropped into an existing project and used. They can also be used as configuration samples for setting up your own containers. (However, see the [vscode-remote-try-*](https://github.com/search?q=org%3Amicrosoft+vscode-remote-try-&type=Repositories) repositories if you are looking for complete sample projects.)
This repository contains a set of **dev container definitions** to help get you up and running with a containerized environment. The definitions describe the appropriate container image, runtime arguments for starting the container, and VS Code extensions that should be installed. They provide a container configuration file (`devcontainer.json`) along with an image, Dockerfile, or Docker Compose file you can drop them into any existing folder as a starting point. If you have an existing Docker setup, you can use them as examples to help you adapt your own configuration. (However, the [vscode-remote-try-*](https://github.com/search?q=org%3Amicrosoft+vscode-remote-try-&type=Repositories) repositories are a better starting point if you are looking for complete sample projects.)

## Using a definition

Expand Down

0 comments on commit c666128

Please sign in to comment.