Docker Guide
This project includes a Docker workflow that will allow you to build a new firmware for your keyboard very easily without major changes to your primary operating system. This also ensures that when you clone the project and perform a build, you have the exact same environment as anyone else and the QMK build infrastructure. This makes it much easier for people to help you troubleshoot any issues you encounter.

Requirements

The main prerequisite is a working docker or podman install.

Usage

Acquire a local copy of the QMK's repository (including submodules):
1
git clone --recurse-submodules https://github.com/qmk/qmk_firmware.git
2
cd qmk_firmware
Copied!
Run the following command to build a keymap:
1
util/docker_build.sh <keyboard>:<keymap>
2
# For example: util/docker_build.sh planck/rev6:default
Copied!
This will compile the desired keyboard/keymap and leave the resulting .hex or .bin file in the QMK directory for you to flash. If :keymap is omitted, all keymaps are used. Note that the parameter format is the same as when building with make.
There is also support for building and flashing the keyboard straight from Docker by specifying the target as well:
1
util/docker_build.sh keyboard:keymap:target
2
# For example: util/docker_build.sh planck/rev6:default:flash
Copied!
You can also start the script without any parameters, in which case it will ask you to input the build parameters one by one, which you may find easier to use:
1
util/docker_build.sh
2
# Reads parameters as input (leave blank for all keyboards/keymaps)
Copied!
You can manually set which container runtime you want to use by setting the RUNTIME environment variable to it's name or path. By default docker or podman are automatically detected and docker is preferred over podman.
1
RUNTIME="podman" util/docker_build.sh keyboard:keymap:target
Copied!

FAQ

Why can't I flash on Windows/macOS

On Windows and macOS, it requires Docker Machine to be running. This is tedious to set up, so it's not recommended; use QMK Toolbox instead.
!> Docker for Windows requires Hyper-V to be enabled. This means that it cannot work on versions of Windows which don't have Hyper-V, such as Windows 7, Windows 8 and Windows 10 Home.
Last modified 9mo ago