Dev Container Templates

Dev Container Templates are sets of source files that encode configuration for a complete development environment. You can use them in two primary ways:

1. Using supporting tools: Tools like Visual Studio Code and GitHub Codespaces provide direct integrations to configure templates hosted in this repository. You can also customize these environments using available Features.
2. Using the Dev Container CLI: Use the @devcontainers/cli to programmatically apply templates from an OCI registry to your project workspace.

The typescript-node template is designed for developing Node.js applications using TypeScript. It provides a pre-configured environment including:

• Node.js
• ESLint
• NVM (Node Version Manager)
• Yarn
• TypeScript compiler

This template uses a pre-built image (mcr.microsoft.com/devcontainers/typescript-node) that automatically includes the necessary devcontainer.json metadata.

The Jekyll template provides a complete environment for developing static sites with Jekyll. It uses a pre-built image that automatically includes the necessary devcontainer.json metadata.

Image Details:

• Image: mcr.microsoft.com/devcontainers/jekyll
• Metadata: Automatically applies devcontainer.json contents from the image.

The Miniconda template is designed for developing applications in Python 3. It provides a development container environment that includes the conda package manager, the Python extension, and automatically installs dependencies from an environment.yml file if present.

Key Details:

• Base Image: mcr.microsoft.com/devcontainers/miniconda
• Automatic Metadata: This template uses a pre-built image that includes necessary devcontainer.json metadata.
• Dependency Management: It automatically processes an environment.yml file located in the parent folder during the build process.

The Markdown template provides a simple container environment optimized for editing markdown files. It uses a pre-built image that includes necessary devcontainer.json metadata automatically.

Template Details:

• Base Image: mcr.microsoft.com/devcontainers/base:debian
• Metadata: The template automatically applies devcontainer.json contents from the base image.

The javascript-node template is designed for developing Node.js based applications. It provides a pre-configured environment that includes:

• Node.js
• eslint
• nvm
• yarn

This template uses a pre-built image (mcr.microsoft.com/devcontainers/javascript-node) that automatically includes the necessary devcontainer.json metadata.

The Default Linux Universal (universal) template provides an Ubuntu-based, large, multi-language container optimized for GitHub Codespaces. It uses a pre-built image that automatically includes necessary devcontainer.json metadata.

Image Details:

• Image: mcr.microsoft.com/devcontainers/universal
• Metadata: Automatically applies devcontainer.json contents from the image.

The dotnet-fsharp template is designed for developing F# and .NET based applications. It provides a development environment that includes all necessary SDKs, extensions, and dependencies.

This template utilizes a pre-built image that automatically includes required devcontainer.json metadata, reducing the need for manual configuration.

Many web frameworks and tools listen only on localhost inside the container. To make these ports accessible on your host machine, use the forwardPorts property in devcontainer.json.

Unlike the ports property in docker-compose.yml (which publishes ports and may require applications to listen on 0.0.0.0 to work in cloud environments like Codespaces), forwardPorts works reliably for local development even if the application is bound to localhost.

"forwardPorts": [9000]

When configuring Kubernetes Ingress within this environment, be aware that Kubernetes binds to a specific interface's IP by default, rather than localhost or all interfaces.

To connect to your services, you must use the Kubernetes Node's IP, even when running a single-node cluster like Minikube.