diff options
| author | Zach White <skullydazed@gmail.com> | 2021-08-29 16:41:56 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-08-29 16:41:56 -0700 |
| commit | b705020dafd0aa7531d03cd8fa64260684a3fb79 (patch) | |
| tree | 81957f7a08a583e39f80ae4c49b61e68e7a18fb7 /docs/getting_started_vagrant.md | |
| parent | 13a2da973f182f238d1e27bd9da6f98173dad026 (diff) | |
move everything from qmkfm/base_container to qmkfm/qmk_cli (#14230)
Diffstat (limited to 'docs/getting_started_vagrant.md')
| -rw-r--r-- | docs/getting_started_vagrant.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/getting_started_vagrant.md b/docs/getting_started_vagrant.md index b71f8908b9..114f875671 100644 --- a/docs/getting_started_vagrant.md +++ b/docs/getting_started_vagrant.md @@ -24,7 +24,7 @@ The "easy" way to flash the firmware is using a tool from your host OS: If you want to program via the command line you can uncomment the ['modifyvm'] lines in the Vagrantfile to enable the USB passthrough into Linux and then program using the command line tools like dfu-util/dfu-programmer or you can install the Teensy CLI version. ## Vagrantfile Overview -The development environment is configured to run the QMK Docker image, `qmkfm/base_container`. This not only ensures predictability between systems, it also mirrors the CI environment. +The development environment is configured to run the QMK Docker image, `qmkfm/qmk_cli`. This not only ensures predictability between systems, it also mirrors the CI environment. ## FAQ |