You can use Docker to build and run code in a clean environment, especially one with different packages. This is especially helpful if your system is not able to run our standard build environment.

Visual Studio Code has excellent integration for Docker. We recommend installing the Docker extension from Microsoft.

Installing Docker

Docker is fairly easy to install on most major operating systems. Installation instructions for Windows, macOS, and the major Linux distributions can be found on the Docker Engine overview | Docker Documentation


Linux users should be sure to follow the guides for Manage Docker as a non-root user and Configure Docker to start on boot outlined on the Post-installation steps for Linux | Docker Documentation.

Docker Registry Login

We host Docker images on our own private registry, which you can log into with your company credentials.

This section describes how to set this up for Linux, specifically Ubuntu, although the instructions should be the same across most distros.

For Windows or macOS, or for more options and information in general, see docker login | Docker Documentation

Installing and Configuring Pass

First, install pass on your system. This should be available in your distribution’s package manager. On Debian-based systems, run:

sudo apt install pass

Download and install the latest version of docker-credential-pass. This is usually downloaded as a precompiled binary and installed in place. The latest version can be found on the docker-credential-helpers GitHub Releases page

The latest installation instructions (as of writing) for most 64-bit systems is as follows:

cd /tmp
tar -xf docker-credential-pass-v0.6.3-amd64.tar.gz
chmod +x docker-credential-pass
sudo mv docker-credential-pass /usr/local/bin/.

Test that this installed correctly by running the following:

docker-credential-pass version

This should print out the version of docker-credential-pass that is installed.

Initializing with GPG Key

You’ll also need a GPG key.

Existing GPG Key

If you already have one created (or if you’re not sure), you can see all the public keys known to your computer with this command:

gpg --list-keys

This will show all public keys known to your computer, including any belonging to other people that you have stored for verification purposes. Scroll through to find your name and email, and then grab your key. (It’s the long value towards the top with all the uppercase numbers and letters).

For example, here’s mine:

pub   rsa3072 2019-04-26 [SC]
uid           [ultimate] Jason C. McDonald <>
uid           [ultimate] [jpeg image of size 4211]
uid           [ultimate] Jason C. McDonald <>
uid           [ultimate] Jason C. McDonald <>
uid           [ultimate] Jason C. McDonald <>
sub   rsa3072 2019-04-26 [E]

So, 7EE3D0EE0FEF8B536A432F975B410ECF0158442A would be my public key. Note, I cannot actually sign anything with that key unless I also have the private key on my system! (Of course, I do.)

If this step worked, skip down to Initialzing Pass.

New GPG Key

If you don’t have a GPG key, you can generate a new one easily:

gpg --gen-key

Press Enter to select the default for the first three options, and then confirm your choices by pressing y and Enter. Now it will prompt you for your real name, email address, and an optional comment.

If you choose, you can also set a passphrase at this time, although it is not required. If you do set a passphrase, be careful not to lose it! There is no way to reset it or recover a password for a GPG key.

At this time, you may see that the computer is trying to “gain entropy”. Just switch to another window or terminal and do other things for a bit. As you use the computer, it’ll create that entropy it needs.

Once you’re done, you’ll see that your key was created. Grab the key from the Look for the line marked pub, and get the key from after the first forward-slash (/).

Initialzing Pass

Initialize pass with the following command, substituting your GPG key in place of MYGPGKEYHERE:


If all goes well, then the following command should work:

docker-credential-pass list

If pass is not configured, you’ll receive a warning like “pass store is uninitialized.”.

Otherwise, if you see {} or other data, it worked!

Make Docker Use Pass

Edit the file ~/.docker/config.json, and set the property "credsStore" to "pass" (Include the quotes!). Save and close the file.

You should now be ready to login with Docker.

Logging Into Registry

Once pass is configured, you can log into the MousePaw Media Registry, which lives at

docker login

At the prompt, enter your company username and password. If login is successful, you will see:

Login Succeeded

You can now work with MousePaw Media’s private Docker image registry.