# devcontainer mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für devcontainer in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:devcontainer
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install devcontainer
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#devcontainer
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/de/devcontainer/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:devcontainer
- **Paketmanager:** Homebrew
- **Version:** 0.88.0
- **Quellzusammenfassung:** Reference implementation for the Development Containers specification
- **Homepage:** <https://containers.dev>
- **Zuletzt aktualisiert:** 2026-07-23T23:57:30Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- devcontainer (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.88.0
## Projektgeschichte und Nutzung

Dev Container CLI is the reference command-line implementation for the Development Containers specification. It reads devcontainer.json metadata and creates, builds, configures, and runs development containers outside a single editor UI.

### Projektgeschichte

The devcontainers/spec repository was created in January 2022, and devcontainers/cli followed in April 2022. The CLI changelog starts with 0.1.0 as the initial version and then quickly adds build, feature, template, metadata, and lifecycle support through the 2022 releases.

### Adoptionsgeschichte

The broader dev container format came from the need for structured metadata that tools could share, similar in spirit to the Language Server Protocol. The official supporting-tools page lists editors and services such as VS Code, Visual Studio, IntelliJ IDEA, GitHub Codespaces, and the standalone Dev Container CLI as participants in the ecosystem.

### Wie es verwendet wird

Package users install the devcontainer executable, keep devcontainer.json in a project, and run commands such as devcontainer up, build, exec, read-configuration, features, and templates. The CLI README also frames it as useful for CI, where a project's development container can be reused as a build and test environment.

### Warum Paket-Nerds sich dafür interessieren

For package nerds, devcontainer is important because it turns editor-oriented development-environment metadata into a portable CLI contract. It bridges package managers, Docker or Podman-style container engines, OCI-distributed features, templates, GitHub Actions, Codespaces, and local development workflows.

### Zeitleiste

- 2022: devcontainers/spec repository created.
- 2022: devcontainers/cli repository created.
- 2022: CLI 0.1.0 initial version appears in the changelog.
- 2022: CLI 0.12.0 added native feature publishing to OCI registries.
- 2026: CLI 0.87.0 made lockfile generation stable by default.

### Related projects

- Officially related projects include the Development Containers specification, Dev Container Features and Templates, devcontainers/ci, VS Code Dev Containers, GitHub Codespaces, Docker, Docker Compose, and supporting IDE integrations.

### Quellen

- <https://containers.dev/>
- <https://containers.dev/overview>
- <https://containers.dev/supporting>
- <https://github.com/devcontainers/cli>
- <https://github.com/devcontainers/cli/blob/main/README.md>
- <https://github.com/devcontainers/cli/blob/main/CHANGELOG.md>
- <https://api.github.com/repos/devcontainers/cli>
- <https://api.github.com/repos/devcontainers/spec>


## Sicherheitshinweise

infrastructure mutation or orchestration signal.

- **Geiger-Risiko:** orange / mittel
- infrastructure mutation or orchestration signal


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: .devcontainer/devcontainer.json, .devcontainer.json
## Andere Paketmanager-Einträge

- Nix - devcontainer: normalized package name match | nixpkgs package indexes: pkgs/by-name/de/devcontainer/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/devcontainer.yml](https://github.com/mxcl/pkgdb/blob/main/combined/devcontainer.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph