summaryrefslogtreecommitdiff
path: root/docs/getting_started_vagrant.md
diff options
context:
space:
mode:
authorRyan <fauxpark@gmail.com>2021-09-14 22:16:24 +1000
committerGitHub <noreply@github.com>2021-09-14 13:16:24 +0100
commitb56282756b5faa410301de8c4ecdcae0e0148652 (patch)
treecf68cfe0e4f148d6eab52ae289ce261bea88f6c3 /docs/getting_started_vagrant.md
parent0ca4a56a0449d17a497ba610d4cee41c914ff50e (diff)
downloadqmk_firmware-b56282756b5faa410301de8c4ecdcae0e0148652.tar.gz
qmk_firmware-b56282756b5faa410301de8c4ecdcae0e0148652.zip
[Docs] Clean up some code block languages (#14434)
Diffstat (limited to 'docs/getting_started_vagrant.md')
-rw-r--r--docs/getting_started_vagrant.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/getting_started_vagrant.md b/docs/getting_started_vagrant.md
index 114f875671..b5b5ce1539 100644
--- a/docs/getting_started_vagrant.md
+++ b/docs/getting_started_vagrant.md
@@ -31,26 +31,26 @@ The development environment is configured to run the QMK Docker image, `qmkfm/qm
### Why am I seeing issues under Virtualbox?
Certain versions of Virtualbox 5 appear to have an incompatibility with the Virtualbox extensions installed in the boxes in this Vagrantfile. If you encounter any issues with the /vagrant mount not succeeding, please upgrade your version of Virtualbox to at least 5.0.12. **Alternately, you can try running the following command:**
-```console
+```
vagrant plugin install vagrant-vbguest
```
### How do I remove an existing environment?
Finished with your environment? From anywhere inside the folder where you checked out this project, Execute:
-```console
+```
vagrant destroy
```
### What if I want to use Docker directly?
Want to benefit from the Vagrant workflow without a virtual machine? The Vagrantfile is configured to bypass running a virtual machine, and run the container directly. Execute the following when bringing up the environment to force the use of Docker:
-```console
+```
vagrant up --provider=docker
```
### How do I access the virtual machine instead of the Docker container?
Execute the following to bypass the `vagrant` user booting directly to the official qmk builder image:
-```console
+```
vagrant ssh -c 'sudo -i'
```