Configuring Codespaces for your project

You can use a devcontainer.json file to define a Codespaces environment for your repository.

People with write permissions to a repository can create or edit the codespace configuration.

Codespaces is available for user accounts using GitHub Free or GitHub Pro. For more information, see "GitHub's products."

In this article

Note: Codespaces is currently in limited public beta and subject to change. During the beta period, GitHub does not make any guarantees about the availability of Codespaces. For more information about joining the beta, see "About Codespaces."

About dev containers

A development container, or dev container, is the environment that Codespaces uses to provide the tools and runtimes that your project needs for development. When working with a dev container in Codespaces you can either use the default configuration, use a pre-defined configuration, or create your own configuration. The option you choose is dependent on the tools, runtimes, dependencies, and workflows that a user might need to be successful with your project.

Codespaces allows for customization on a per-project and per-branch basis with a devcontainer.json file. This configuration file determines the environment of every new codespace anyone creates for your repository by defining a development container that can include frameworks, tools, extensions, and port forwarding. A Dockerfile can also be used alongside the devcontainer.json file in the .devcontainer folder to define everything required to create a container image.


This file can be located in the root of the repository or in a folder called .devcontainer. If the file is located in the root of the repository, the filename must begin with a period: .devcontainer.json.

You can use your devcontainer.json to set default settings for the entire codespace environment, including the editor, but you can also set editor-specific settings for individual workspaces in a codespace in a file named .vscode/settings.json.

For information about the settings and properties that you can set in a devcontainer.json, see devcontainer.json reference in the Visual Studio Code documentation.


A Dockerfile also lives in the .devcontainer folder.

You can add a Dockerfile to your project to define a container image and install software. In your Dockerfile, use FROM to designate the image, and the RUN instruction to install any software. For example:


# ** [Optional] Uncomment this section to install additional packages. **
# USER root
# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
#     && apt-get -y install --no-install-recommends <your-package-list-here>
# USER codespace

Reference your Dockerfile in your devcontainer.json file by using the dockerfile property.

  "build": { "dockerfile": "Dockerfile" },

For more information on using a Dockerfile in a dev container, see in the Visual Studio Code documentation.

Using the default configuration

If you don't define a configuration in your repository, GitHub creates a codespace with a base Linux image. The base Linux image includes languages and runtimes like Python, Node.js, JavaScript, TypeScript, C++, Java, .NET, PHP, PowerShell, Go, Ruby, and Rust. It also includes other developer tools and utilities like git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the devcontainer-info content-url command inside your codespace terminal and follow the url.

For more information about everything that is included in the base Linux image, see the latest file in the microsoft/vscode-dev-containers repository.

The default configuration is a good option if you're working on a small project that uses the languages and tools that Codespaces provides.

Using a predefined container configuration

Predefined container definitions include a common configuration for a particular project type, and can help you quickly get started with a configuration that already has the appropriate container options, Visual Studio Code settings, and Visual Studio Code extensions that should be installed.

Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project's setup.

  1. To access the command palette, in the upper-left corner, select the Application Menu and click Command Palette… from the View menu, then start typing "Codespaces: Add Development Container Configuration Files...". Click Codespaces: Add Development Container Configuration Files... "Codespaces: Add Development Container Configuration Files..." in the command palette
  2. Click the definition you want to use. List of predefined container definitions
  3. Follow the prompts to customize your definition.
  4. Click OK. OK button
  5. To apply the changes, in the bottom right corner of the screen, click Rebuild now. For more information about rebuilding your container, see "Applying changes to your configuration." "Codespaces: Rebuild Container" in the command palette

Creating a custom codespace configuration

If none of the predefined configurations meet your needs, you can create a custom configuration by adding a devcontainer.json file. This file can be located in the root of the repository or in a folder called .devcontainer. If the file is located in the root of the repository, the filename must begin with a period: .devcontainer.json.

In the file, you can use supported configuration keys to specify aspects of the codespace's environment, like which Visual Studio Code extensions will be installed.

When you configure editor settings for Visual Studio Code, there are three scopes available: Workspace, Remote [Codespaces], and User. If a setting is defined in multiple scopes, Workspace settings take priority, then Remote [Codespaces], then User.

You can define default editor settings for Visual Studio Code in two places.

  • Editor settings defined in .vscode/settings.json are applied as Workspace-scoped settings in the codespace.
  • Editor settings defined in the settings key in devcontainer.json are applied as Remote [Codespaces]-scoped settings in the codespace.

After updating the devcontainer.json file, you can rebuild the container for your codespace to apply the changes. For more information, see "Applying changes to your configuration."

Applying changes to your configuration

After the Codespaces configuration for a repository changes, you can apply the changes to an existing codespace by rebuilding the container for the codespace.

  1. Access the command palette (shift command P / shift control P), then start typing "Codespaces: Rebuild Container". Click Codespaces: Rebuild Container. "Codespaces: Rebuild Container" in the command palette
  2. If changes to your codespace's configuration cause a container error, your codespace will run in recovery mode, and you will see an error message. Fix the errors in the configuration. Error message about recovery mode
    • To diagnose the error by reviewing the creation logs, click View creation log.
    • To fix the errors identified in the logs, update your devcontainer.json file.
    • To apply the changes, rebuild your container. Access the command palette (shift command P / shift control P), then start typing "Codespaces: Rebuild Container". Click Codespaces: Rebuild Container.

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.