Skip to content

Commit c71ae87

Browse files
committed
replace BASE_BOX with FROM_SCRATCH, add PREBUILT_VERSION, and add small troubleshooting tip for NO_SUBMISSIONS=1 for git troubles
1 parent d96d8c4 commit c71ae87

File tree

2 files changed

+22
-2
lines changed

2 files changed

+22
-2
lines changed

_docs/developer/getting_started/vm_install_using_vagrant.md

+11-2
Original file line numberDiff line numberDiff line change
@@ -228,11 +228,20 @@ Below are quick steps to get everything installed and running.
228228
229229
If you wish to run `vagrant up` from scratch, on Linux or Mac type:
230230
```
231-
BASE_BOX=1 vagrant up
231+
FROM_SCRATCH=1 vagrant up
232232
```
233233
or on Windows, type:
234234
```
235-
SET BASE_BOX=1
235+
SET FROM_SCRATCH=1
236+
vagrant up
237+
```
238+
If you wish to use a specific version of the pre-packaged Submitty VM, on Linux or Mac type:
239+
```
240+
PREBUILT_VERSION={version} vagrant up
241+
```
242+
or on Windows, type:
243+
```
244+
SET PREBUILT_VERSION={version}
236245
vagrant up
237246
```
238247
This process will take anywhere from 30 minutes to a few hours depending on your

_docs/developer/troubleshooting/installation_troubleshooting.md

+11
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,17 @@ with no explanation, then there are a couple of things that may be going wrong:
4444
This will delete all virtual machine settings. Then install
4545
the latest version of Virtual Box and vagrant from the links given in step 3 (using Ubuntu Software).
4646

47+
* If you are not using the prebuilt Submitty VM, and you get an error like
48+
```
49+
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpad2cfj3v/abernl'
50+
```
51+
This is a known issue with our implementation of Git gradeables, which will be resolved when we have the time. Until then, you can do.
52+
```
53+
NO_SUBMISSIONS=1 vagrant up
54+
```
55+
56+
__This will not have submissions in the VM, so you will have to manually add some__
57+
4758
* If it has been a while since your last `vagrant destroy` and
4859
`vagrant up` you may need to update/upgrade/reinstall the virtual
4960
box, vagrant, and the installed boxes on your

0 commit comments

Comments
 (0)