Building Docker images from private GitHub repos

Docker has a nice build context feature that lets you specify a git repository URL as the location to build an image from. So, for instance, you can roll your own Redis image like this:

docker build -t myredis:5

But things get more complicated if you want to build from a private repository, and more complicated again if you have to deal with SSO.

Let’s take the first case: you want to build from a private repository that doesn’t have SSO enabled. The only change here is that you need to specify your access credentials in the URL, like this:

docker build https://${USER}:${PASS}

It’s probably not a good idea to use your actual access credentials here because 1) these generally have more privileges than Docker needs and 2) bad things might happen if someone else were to get their hands on them. Instead, you should consider creating a one-off set of credentials with minimal privileges. If you’re using GitHub, then you can do this by creating a personal access token (e.g. with repo permissions only) and use this in place of your regular password.

Now, consider the second case: your repository is private and access is restricted with SSO. The build line above now fails because your credentials must be further verified via SSO. To get around this, you need to authorise your credentials so that they can be used without requiring manual intervention for SSO. Again, if you’re using GitHub, you can enable SSO for your personal access tokens pretty easily.

Finally, if you’re using Docker Compose, then you can automate this whole process by creating a .env file containing your credentials, like this:


And then defining the corresponding build context, like this:

version: ...

      context: https://{USER}:{PASS}