- Notifications
You must be signed in to change notification settings - Fork405
Development Containers: Use a container as a full-featured development environment.
License
CC-BY-4.0, MIT licenses found
Licenses found
devcontainers/spec
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
This repository is for the Development Container Specification. You can check out the spec on our websitehttps://containers.dev/ too.
A development container allows you to use a container as a full-featured development environment. It can be used to run an application, to separate tools, libraries, or runtimes needed for working with a codebase, and to aid in continuous integration and testing.
The Development Container Specification seeks to find ways to enrich existing formats with common development specific settings, tools, and configuration while still providing a simplified, un-orchestrated single container option – so that they can be used as coding environments or for continuous integration and testing.
The first format in the specification,devcontainer.json, was born out of necessity. It is a structured JSON with Comments (jsonc) metadata format that tools can use to store any needed configuration required to develop inside of local or cloud-based containerized coding.
We envision that this same structured data can be embedded in images and other formats – all while retaining a common object model for consistent processing. For example, some of this same metadata can be added to adevcontainer.metadata image label to tie settings directly to a container image.
Beyond repeatable setup, these same development containers provide consistency to avoid environment specific problems across developers and centralized build and test automation services. You can use theopen-source CLI reference implementation either directly or integrated into product experiences to use the structured metadata to deliver these benefits. It currently supports integrating with Docker Compose and a simplified, un-orchestrated single container option – so that they can be used as coding environments or for continuous integration and testing.
A GitHub Action and an Azure DevOps Task are available indevcontainers/ci for running a repository's dev container in continuous integration (CI) builds. This allows you to reuse the same setup that you are using for local development to also build and test your code in CI.
You may review the specification in thedocs/specs folder of this repo.
You may also review active proposals in theproposals folder.
Images used in this repo will be contained in theimages folder. The icon for thedev container GitHub org is from theFluent icon library.
If you are interested in contributing, please check out theHow to Contribute document, open an issue, orjoin our community Slack channel.
Please report issues in the following repositories:
- Spec-maintained Features and Templates:devcontainers/features,devcontainers/templates
- CLI reference implementation and non-spec related feature requests:devcontainers/cli
- GitHub Action and Azure DevOps Task:devcontainers/ci
License for this repository:
Copyright © Microsoft Corporation All rights reserved.
Creative Commons Attribution 4.0 License (International):https://creativecommons.org/licenses/by/4.0/legalcode
About
Development Containers: Use a container as a full-featured development environment.
Topics
Resources
License
CC-BY-4.0, MIT licenses found
Licenses found
Code of conduct
Contributing
Security policy
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Uh oh!
There was an error while loading.Please reload this page.
