DEV Community

loading...

Using Devcontainer With GitHub Codespaces

Ruairí O'Brien
Originally published at ruarfff.com Updated on ・3 min read

A while back I started using Devcontainer in VsCode. I really liked the editor integration and if you're in a team, being able to share the development environment like this is great. We have been able to do this for a while now with docker or even vagrant but getting a nice editor abstraction makes it easier to adopt.

I recently got access to Codespaces and discovered it also supports this setup.

I am using it for this python repo. There is also a more detail official example.

If you don't have access to Codespaces you can request early access - note that link may not age well.

If you have access, you should see an option in the GitHub UI:

Alt Text

If you have not setup this repo before, you will be asked to create a new Codespace. After that, you will have a link to the space like this:

Alt Text

Then you basically have VSCode in the browser:

Alt Text

You don't need any extra setup for this to work. You will get a handy development environment that persists so you can open it up on any machine with a browser without needing to install any extra development tools. You can work on one machine and move to another no problem.

What if you want to customise the setup? That's where devcontainer comes in. For my example repo, I wanted to use python 3.8 and I wanted pipenv to be installed. This is how I set that up.

Docker Setup

You can define the environment you want to use for development with a dockerfile. My docker file it really basic but you can do whatever you need here:

FROM python:3.8

RUN  pip install pipenv
Enter fullscreen mode Exit fullscreen mode

I put this at the root of the project in a file called Dockerfile.

For Codespaces to use this you need one more step.

Create a file: .devcontainer/devcontainer.json

{
    "name": "Docker Setup",

    // Sets the run context to one level up instead of the .devcontainer folder so we can keep Dockerfile at the root.
    "context": "..",

    // Set *default* container specific settings.json values on container create.
    "settings": {
        "terminal.integrated.shell.linux": null
    },

    "extensions": [],

    "postCreateCommand": "pipenv sync --dev",

    "runArgs": [ "--network", "host"],
}
Enter fullscreen mode Exit fullscreen mode

I like having the Dockerfile at the root of my project so I configured it that way but it's also quite common to put the Dockerfile in the .devcontainers directory.

"terminal.integrated.shell.linux": null just says we don't want to use my local VSCode shell settings since your own VSCode settings get imported if you are using settings sync. You can configure this to be more specific based on what's in your Dockerfile.

I want to use pipenv so having this run post creation "postCreateCommand": "pipenv sync --dev" saves one extra step.

"runArgs": [ "--network", "host"] because I don't want to bother messing with ports.

With all that setup, once you create a new Codespace, you should see it getting created like this:

Alt Text

Now you have an environment setup the way you want.

This is a very basic example but there's a lot more you can do.

More Customisation

You will almost certainly want to look at setting up GitHub dotfiles to customise the shell in Codespaces.

Checkout the many examples in the vscode-dev-containers repo.

Discussion (0)

Forem Open with the Forem app