logo

qmk_firmware

custom branch of QMK firmware git clone https://anongit.hacktivis.me/git/qmk_firmware.git

getting_started_docker.md (2995B)

    

  1. # Docker Quick Start
  3. 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.
  5. ## Requirements
  7. The main prerequisite is a working `docker` or `podman` install.
  9. * [Docker CE](https://docs.docker.com/install/#supported-platforms)
  10. * [Podman](https://podman.io/getting-started/installation)
  12. ## Usage
  14. Acquire a local copy of the QMK's repository (including submodules):
  16. ```
  17. git clone --recurse-submodules https://github.com/qmk/qmk_firmware.git
  18. cd qmk_firmware
  19. ```
  21. Run the following command to build a keymap:
  23. ```
  24. util/docker_build.sh <keyboard>:<keymap>
  25. # For example: util/docker_build.sh planck/rev6:default
  26. ```
  28. 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`.
  30. There is also support for building _and_ flashing the keyboard straight from Docker by specifying the `target` as well:
  32. ```
  33. util/docker_build.sh keyboard:keymap:target
  34. # For example: util/docker_build.sh planck/rev6:default:flash
  35. ```
  37. Note that mass storage bootloaders are not supported by the `flash` target. In this case you will have to manually copy the firmware file to the keyboard.
  39. 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:
  41. ```
  42. util/docker_build.sh
  43. # Reads parameters as input (leave blank for all keyboards/keymaps)
  44. ```
  46. You can manually set which container runtime you want to use by setting the `RUNTIME` environment variable to it's name or path.
  47. By default docker or podman are automatically detected and docker is preferred over podman.
  49. ```
  50. RUNTIME="podman" util/docker_build.sh keyboard:keymap:target
  51. ```
  53. If flashing is not required, it's possible to run the container as unprivileged (on Linux), and without docker-machine (on Windows/macOS):
  55. ```
  56. SKIP_FLASHING_SUPPORT=1 util/docker_build.sh keyboard:keymap:target
  57. ```
  60. ## FAQ
  62. ### Why can't I flash on Windows/macOS
  64. On Windows and macOS, it requires [Docker Machine](http://gw.tnode.com/docker/docker-machine-with-usb-support-on-windows-macos/) to be running. This is tedious to set up, so it's not recommended; use [QMK Toolbox](https://github.com/qmk/qmk_toolbox) instead.
  66. ::: warning
  67. Docker for Windows requires [Hyper-V](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-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**.
  68. :::