A collection of Dev Container Features managed by Dev Container spec maintainers. See https://github.com/devcontainers/feature-starter to publish your own
Find a file
github-actions[bot] d10390a141
Automated documentation update (#81)
Co-authored-by: github-actions <github-actions@github.com>
2022-08-06 00:09:59 +00:00
.github Prep: republish features to ghcr.io (#78) 2022-08-05 15:22:30 -04:00
.vscode Update launch.json 2022-05-12 20:49:10 -04:00
src Automated documentation update (#81) 2022-08-06 00:09:59 +00:00
test Rename feature: 'common' to 'common-utils' (#79) 2022-08-05 18:11:46 +00:00
test-scenarios Rename feature: 'common' to 'common-utils' (#79) 2022-08-05 18:11:46 +00:00
.gitignore add v2 action 2022-06-03 14:49:26 +00:00
CODEOWNERS Adds CODEOWNER (#69) 2022-07-27 21:31:23 +00:00
LICENSE Create LICENSE (#54) 2022-06-29 12:59:43 -04:00
README.md Update README.md 2022-07-29 13:52:13 -04:00

Development Container Features

devcontainers organization logo Development Container 'Features'
A set of simple and reusable 'features'. Quickly add a language/tool/CLI to a development container.

'Features' are self-contained units of installation code and development container configuration. Features are designed to install atop a wide-range of base container images (this repo focuses on debian based images).

Missing a CLI or language in your otherwise perfect container image? Add the relevant 'feature' to the features property of a devcontainer.json. A tool supporting the dev container specification is required to build a development container.

⚠️ Development container 'features' are a proposed addition to the development container specification. Please note that 'features' are in preview and subject to breaking changes.

Once the proposed specification is accepted, implementation details will be published at https://containers.dev.

Repo Structure

.
├── lib
|   ├── settings.env
|   ├── utils.sh
│   └── ...
├── README.md
├── src
│   ├── dotnet
│   │   ├── devcontainer-feature.json
│   │   └── install.sh
│   ├── go
│   │   ├── devcontainer-feature.json
│   │   └── install.sh
|   ├── ...
│   │   ├── devcontainer-feature.json
│   │   └── install.sh
├── test
│   ├── dotnet
│   │   └── test.sh
│   └── go
│   |   └── test.sh
|   ├── ...
│   │   └── test.sh
├── test-scenarios
│   ├── install_jupyterlab.sh
│   ├── install_python_twice.sh
|   ├── ...
│   └── scenarios.json
  • lib - A collection of tools, scripts, and shared configuration used generally by this repo's features.
  • src - A collection of subfolders, each declaring a feature. Each subfolder contains at least a devcontainer-feature.json and the appropriately declared install script.
  • test - Mirroring src, a folder-per-feature with at least a test.sh script. The devcontainer CLI will execute these tests in CI.
  • test-scenarios - More complex scenarios involving a set of features from this repo. The devcontainer CLI will execute these tests in CI.

Usage

To reference a feature from this repository, add the desired features to a devcontainer.json.

The example below installs the go and docker-in-docker declared in the ./src directory of this repository.

See the relevant feature's README for supported options.

"name": "my-project-devcontainer",
"image": "mcr.microsoft.com/devcontainers/base:ubuntu",  // Any generic, debian-based image.
features: {
    "devcontainers/features/go@latest": {
        "version": "1.18"
    },
    "devcontainers/features/docker-in-docker@latest": {
        "version": "latest",
        "moby": true
    }
}

The @latest version annotation is added implicitly if omitted. To pin to a specific release tag, append it to the end of the feature.

features: {
    "devcontainers/features/go@v0.0.2": {
        "version": "1.18"
    },

The devcontainer CLI reference implementation (or a supporting tool) can be used to build a project's dev container declaring 'features'.

git clone <my-project-with-devcontainer>
devcontainer build --workspace-folder <path-to-my-project-with-devcontainer>

Contributions

Contibuting to this repository

This repository will accept improvement and bug fix contributions related to the current set of maintained features.

Creating your own collection of features

Please see the proposed specification on how to author and distribute features, as well as our GitHub Action, which serves as a reference implementation for the distribution portion of the specification.