IMPORTANT NOTE: We're starting to migrate contents of this repo to the devcontainers org, as part of the work on the open dev container specification.

We'll now be publishing the base:debian image from devcontainers/images/src/base-debian.

For more details, you can review the announcement issue.

Simple Debian container with Git installed.

See history for information on the contents of published images.

While the definition itself works unmodified, you can select the version of Debian the container uses by updating the VARIANT arg in the included devcontainer.json (and rebuilding if you've already created the container).

"args": { "VARIANT": "buster" }

You can also directly reference pre-built versions of .devcontainer/base.Dockerfile by using the image property in .devcontainer/devcontainer.json or updating the FROM statement in your own Dockerfile to one of the following. An example Dockerfile is included in this repository.

• mcr.microsoft.com/vscode/devcontainers/base:debian (latest)
• mcr.microsoft.com/vscode/devcontainers/base:bullseye (or debian-11)
• mcr.microsoft.com/vscode/devcontainers/base:buster (or debian-10)

You can decide how often you want updates by referencing a semantic version of each image. For example:

• mcr.microsoft.com/vscode/devcontainers/base:0-buster
• mcr.microsoft.com/vscode/devcontainers/base:0.201-buster
• mcr.microsoft.com/vscode/devcontainers/base:0.201.5-buster

See history for information on the contents of each version and here for a complete list of available tags.

Alternatively, you can use the contents of base.Dockerfile to fully customize your container's contents or to build it for a container host architecture not supported by the image.

Beyond git, this image / Dockerfile includes zsh, Oh My Zsh!, a non-root vscode user with sudo access, and a set of common dependencies for development.

Just follow these steps:

1. If this is your first time using a development container, please see getting started information on setting up Remote-Containers or creating a codespace using GitHub Codespaces.

2. To use the pre-built image:

   1. Start VS Code and open your project folder or connect to a codespace.
   2. Press F1 select and Add Development Container Configuration Files... command for Remote-Containers or Codespaces.
   3. Select this definition. You may also need to select Show All Definitions... for it to appear.

3. To build a custom version of the image instead:

   1. Clone this repository locally.
   2. Start VS Code and open your project folder or connect to a codespace.
   3. Use your local operating system's file explorer to drag-and-drop the locally cloned copy of the .devcontainer folder for this definition into the VS Code file explorer for your opened project or codespace.
   4. Update .devcontainer/devcontainer.json to reference "dockerfile": "base.Dockerfile".

4. After following step 2 or 3, the contents of the .devcontainer folder in your project can be adapted to meet your needs.

5. Finally, press F1 and run Remote-Containers: Reopen Folder in Container or Codespaces: Rebuild Container to start using the definition.

Copyright (c) Microsoft Corporation. All rights reserved.

Licensed under the MIT License. See LICENSE