spec

spec copied to clipboard

devcontainer-feature.json : Add a new 'alias' property to allow Feature renames

5

Reported in https://github.com/devcontainers/features/issues/123, there is a request to rename an existing Feature (`docker-from-docker` to `docker-outside-of-docker`). Currently, if we simply rename all the `docker-from-docker` references (ie. source code, and Features metadata)...

samruddhikhandale

Add support for devices in devcontainer-feature.json

4

While implementing a [Dev Container feature for Tailscale](https://github.com/tailscale/codespace/pull/6), I discovered that there's no way to have the feature add the equivalent of `runArgs: ["--device=/dev/net/tun"]`, even though you can set `privileged`...

zombiezen

Publish the JSON schema for `devcontainer-feature.json`

1

Context in the [`#devcontainer-community` Slack](https://github.slack.com/archives/C0431R35H37/p1668976861746579) Similar to the `devcontainer.json` schema, publish the schema for [`devcontainer-feature.json`](https://containers.dev/implementors/features/#devcontainer-feature-json-properties). Supporting tools (eg: The Dev Containers VS Code extension) can then pick up this schema...

joshspicer

ref: https://github.com/devcontainers/spec/issues/140 A schema generated from https://github.com/devcontainers/cli/blob/main/src/spec-configuration/containerFeaturesConfiguration.ts#L25-L72 An example of this JSON file "in the wild" can be found in the [devcontainers/features](https://github.com/devcontainers/features/blob/main/src/docker-in-docker/devcontainer-feature.json) repo.

joshspicer

Proposal: enable optional bind mounts

15

When specifying mounts in `devcontainer.json`, we can use `volume` or `bind` mounts: ```jsonc "mounts": [ // Keep command history {"type":"volume", "source": "my-bash-history", "target":"/home/vscode/commandhistory"}, // Mounts the login details from the...

stuartleeks

Addition of "extends" top level property to enable simple configuration inheritance

12

# Problem Multiple teams collaborating on a common codebase may have different dependency or setup needs and currently this is done by sharing a single `devcontainer.json` configuration with all of...

greggroth

Share code between features

7

# Motivation While devcontainers features aim to enable modern software development, the feature code itself is stuck in a lot of code duplication. For example we can find `# Determine...

AlexanderLanin

As we grow the spec and receive great questions from the community, it'll be great to "doc-ify" some of our discussions. We could add a "How to" section to https://containers.dev/,...

bamurtaugh

Not sure about other users, the few requirements I often care about (on NVIDIA GPUs) are as follow: 1. Number of GPU units 2. GPU architecture 3. GPU memory 4....

chrmarti

Context in the [#devcontainer-community Slack](https://github.slack.com/archives/C0431R35H37/p1669228846546309) With me currently trying to reuse a global dotnet tool that is a fake/testing SMTP server, which is useful for testing code that sends out...

warrenbuckley