To reference a Feature from this repository, add the desired Features to a devcontainer.json. Each Feature has a README.md that shows how to reference the Feature and which options are available for that Feature.

Features are referenced in a user’s devcontainer.json under the top level features object. A user can specify an arbitrary number of Features. At build time, these Features will be installed in an order defined by a combination of the installation order rules and implementation.

September 15, 2022 - Referencing different Features from the devcontainers/features repository is as simple as adding a features property to your devcontainer.json. Each Feature has a README.md that shows how to reference the Feature and which options are available for it.

Development containers documentation and specification page.

To make the changes take effect in existing codespaces, you will need to pull the updates to the devcontainer.json file into your codespace, then rebuild the container for the codespace. For more information, see Introduction to dev containers. ... To add features in VS Code while you are working locally, and not connected to a codespace, you must have the "Dev Containers" extension installed and enabled.

December 31, 2025 - Learn how to develop and publish custom Dev Container Features for VS Code, using the Amazon Q CLI feature as a practical example. Includes forking, feature creation, publishing to GHCR, and submitting to the official features index. Tagged with ...

January 21, 2023 - Features are referenced in the features section of the devcontainer.json file. They always follow a specific structure: 1"feature-id": { 2 // options, as JSON key-value pairs 3}

November 3, 2021 - To learn more about creating devcontainer.json files, see Create a Development Container. Development container "Features" are self-contained, shareable units of installation code and dev container configuration.

3 weeks ago - This provides: Modularity: Tools are installed as independent units. Reusability: The same feature can be shared across multiple images. Version Control: Exact feature versions are locked with cryptographic hashes.

3 weeks ago - Sources: docs/specs/devcontainer-features.md248-258 · The options property in devcontainer-feature.json defines user-configurable parameters.

The option name is captialized and sanitized according to option resolution. #!/bin/bash echo "Activating feature 'color'" echo "The provided favorite color is: ${FAVORITE}" ... Features are individually versioned by the version attribute in a Feature's devcontainer-feature.json.

{ "image": "mcr.microsoft.com/devcontainers/base:ubuntu", "features": { "ghcr.io/shinepukur/devcontainer-features/vale:1": { // specify here any options you would like to set for the feature "version": "latest" } } }

November 24, 2022 - Now for any project I want shellcheck for all I need to do is add a line to my features key in the devcontainer.json file and I'm off to the races. "features": { "ghcr.io/lukewiwa/features/shellcheck:0": {} } The second feature was adding the wait-for-it tool. This one required adding an entrypoint and a few options for what host and port to wait for.

Features are predefined scripts that you can add to your devcontainer.json file that will add something to the base image or existing Dockerfile that you are using for a devcontainer.

December 2, 2022 - The new feature can be added by referencing the package URL: ghcr.io/devcontainers/features/azure-cli:1. Dev Container Features are published as GitHub packages · It accepts two new options: extensions and installBicep.

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 in devcontainers/ci for running a repository's dev container in continuous integration (CI) builds.

While devcontainer.json does not focus on hardware or VM provisioning, it can be useful to know your container’s minimum RAM, CPU, and storage requirements. This is what the hostRequirements properties allow you to do. Cloud services can use these properties to automatically default to the best compute option ...

"documentationURL": "https://github.com/devcontainers/features/tree/main/src/python", "description": "Installs the provided version of Python, as well as PIPX, and other common Python utilities. JupyterLab is conditionally installed with the python feature. Note: May require source code compilation.", "options": { "version": { "type": "string", "proposals": [ "latest", "os-provided", "none", "3.12", "3.11", "3.10", "3.9", "3.8", "3.7", "3.6" ], "default": "os-provided", "description": "Select a Python version to install."

May 5, 2025 - It contains the metadata and settings required to create and configure development containers with consistent, reproducible development environments across different tools and platforms. This document provides a comprehensive reference for the properties and options available in the devcontainer.json format. For information about creating and authoring Features that can be referenced in devcontainer.json, see Features System.