From 073935bdbf32bab89ac4cf2561f73834cd31fe00 Mon Sep 17 00:00:00 2001 From: roye2 <07eeroy@gmail.com> Date: Tue, 9 Jun 2026 09:15:17 -0400 Subject: [PATCH 1/6] added docs about changing pre-packaged vm version --- .../installation_troubleshooting.md | 35 +++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/_docs/developer/troubleshooting/installation_troubleshooting.md b/_docs/developer/troubleshooting/installation_troubleshooting.md index 396f235d..c3c52712 100644 --- a/_docs/developer/troubleshooting/installation_troubleshooting.md +++ b/_docs/developer/troubleshooting/installation_troubleshooting.md @@ -289,3 +289,38 @@ Some things to check: rm -rf /Users/MY_HOME_DIRECTORY/.vagrant.d/ rm -rf /Users/MY_HOME_DIRECTORY/.gem/specs/rubygems.org%443/quick/Marshal.4.8/vagrant-vbguest-0.31.0.gemspec ``` +___ + +## Troubleshooting Pre-Packaged VM + +Some issues with the pre-packaged VM can be fixed by installing a different version. Once you've installed a pre-packaged VM, it does not recieve version updates, so it can be a good idea to update the pre-packaged version periodically. To see your current VM version, +run `vagrant up` and look at the output. You should see something like `==> ubuntu-22.04: Checking if box 'SubmittyBot/ubuntu22-dev' version '26.06.00.2606070357' is up to date...`. In this case `26.06.00.2606070357` is the version number. + +### Instructions for Changing the Pre-Packaged VM Version + +From your main Submitty repository, e.g. `/GIT_CHECKOUT/Submitty/`, run: + +``` +vagrant destroy +``` + +This will destroy your current VM and reset the Vagrant environment. + +*Note: If you have more than one VM (perhaps by accident), you can see a list of VMs with the command* `vagrant global-status`. *VMs listed will be given a unique id. You can then run* `vagrant destroy 1a2b3c4d`. *Replace* `1a2b3c4d` *with the id of the VM you wish to destroy.* + +on Linux/MacOS, type: +``` +PREBUILT_VERSION={version} vagrant up --provider=virtualbox +``` + +or on Windows, type: +``` +SET PREBUILT_VERSION={version} +vagrant up --provider=virtualbox +``` + +If you are importing a new version, it will take approximately 30 minutes to download. + +*The version must be only the numbers, not including the* `v` *in front, for example* `26.06.00.2606070357` *not* `v26.06.00.2606070357`. + +*Note: You can find pre-packaged Submitty VM versions on the [Hashicorp Vagrant Box Catalog](https://portal.cloud.hashicorp.com/vagrant/discover/SubmittyBot/ubuntu22-dev) by navigating to the 'Versions' tab in the sidebar. Make sure to follow the [Submitty installation instructions](/developer/getting_started/installation) when setting up your development environment.* From 1415f2e05d318133d56db995b4edf956277773d8 Mon Sep 17 00:00:00 2001 From: roye2 <07eeroy@gmail.com> Date: Tue, 9 Jun 2026 09:20:46 -0400 Subject: [PATCH 2/6] fixed broken link --- _docs/developer/troubleshooting/installation_troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/developer/troubleshooting/installation_troubleshooting.md b/_docs/developer/troubleshooting/installation_troubleshooting.md index c3c52712..1fc62f35 100644 --- a/_docs/developer/troubleshooting/installation_troubleshooting.md +++ b/_docs/developer/troubleshooting/installation_troubleshooting.md @@ -323,4 +323,4 @@ If you are importing a new version, it will take approximately 30 minutes to dow *The version must be only the numbers, not including the* `v` *in front, for example* `26.06.00.2606070357` *not* `v26.06.00.2606070357`. -*Note: You can find pre-packaged Submitty VM versions on the [Hashicorp Vagrant Box Catalog](https://portal.cloud.hashicorp.com/vagrant/discover/SubmittyBot/ubuntu22-dev) by navigating to the 'Versions' tab in the sidebar. Make sure to follow the [Submitty installation instructions](/developer/getting_started/installation) when setting up your development environment.* +*Note: You can find pre-packaged Submitty VM versions on the [Hashicorp Vagrant Box Catalog](https://portal.cloud.hashicorp.com/vagrant/discover/SubmittyBot/ubuntu22-dev) by navigating to the 'Versions' tab in the sidebar. Make sure to follow the [Submitty installation instructions](/developer/getting_started/vm_install_using_vagrant) when setting up your development environment.* From 62c55a87ab9a359d735fd2850f67ef28ffdb0ef2 Mon Sep 17 00:00:00 2001 From: roye2 <07eeroy@gmail.com> Date: Tue, 9 Jun 2026 09:28:34 -0400 Subject: [PATCH 3/6] update wording --- _docs/developer/troubleshooting/installation_troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/developer/troubleshooting/installation_troubleshooting.md b/_docs/developer/troubleshooting/installation_troubleshooting.md index 1fc62f35..75e380da 100644 --- a/_docs/developer/troubleshooting/installation_troubleshooting.md +++ b/_docs/developer/troubleshooting/installation_troubleshooting.md @@ -293,7 +293,7 @@ ___ ## Troubleshooting Pre-Packaged VM -Some issues with the pre-packaged VM can be fixed by installing a different version. Once you've installed a pre-packaged VM, it does not recieve version updates, so it can be a good idea to update the pre-packaged version periodically. To see your current VM version, +Some issues with the pre-packaged VM can be fixed by installing a different version. Once you've installed a pre-packaged VM, it does not recieve version updates, so it can also be a good idea to update the pre-packaged version periodically. To see your current VM version, run `vagrant up` and look at the output. You should see something like `==> ubuntu-22.04: Checking if box 'SubmittyBot/ubuntu22-dev' version '26.06.00.2606070357' is up to date...`. In this case `26.06.00.2606070357` is the version number. ### Instructions for Changing the Pre-Packaged VM Version From d1a38fbcd08084a8250b2a8043972db203b657e9 Mon Sep 17 00:00:00 2001 From: roye2 <07eeroy@gmail.com> Date: Tue, 9 Jun 2026 09:30:07 -0400 Subject: [PATCH 4/6] fix extra line break --- .../developer/troubleshooting/installation_troubleshooting.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/_docs/developer/troubleshooting/installation_troubleshooting.md b/_docs/developer/troubleshooting/installation_troubleshooting.md index 75e380da..98e1fe09 100644 --- a/_docs/developer/troubleshooting/installation_troubleshooting.md +++ b/_docs/developer/troubleshooting/installation_troubleshooting.md @@ -293,8 +293,7 @@ ___ ## Troubleshooting Pre-Packaged VM -Some issues with the pre-packaged VM can be fixed by installing a different version. Once you've installed a pre-packaged VM, it does not recieve version updates, so it can also be a good idea to update the pre-packaged version periodically. To see your current VM version, -run `vagrant up` and look at the output. You should see something like `==> ubuntu-22.04: Checking if box 'SubmittyBot/ubuntu22-dev' version '26.06.00.2606070357' is up to date...`. In this case `26.06.00.2606070357` is the version number. +Some issues with the pre-packaged VM can be fixed by installing a different version. Once you've installed a pre-packaged VM, it does not recieve version updates, so it can also be a good idea to update the pre-packaged version periodically. To see your current VM version, run `vagrant up` and look at the output. You should see something like `==> ubuntu-22.04: Checking if box 'SubmittyBot/ubuntu22-dev' version '26.06.00.2606070357' is up to date...`. In this case `26.06.00.2606070357` is the version number. ### Instructions for Changing the Pre-Packaged VM Version From 7bd90ca63153a9c1662322650d37c5c00799cfda Mon Sep 17 00:00:00 2001 From: roye2 <07eeroy@gmail.com> Date: Wed, 10 Jun 2026 12:25:17 -0400 Subject: [PATCH 5/6] updated to include more vagrant commands --- .../installation_troubleshooting.md | 28 ++++++++++++++++--- 1 file changed, 24 insertions(+), 4 deletions(-) diff --git a/_docs/developer/troubleshooting/installation_troubleshooting.md b/_docs/developer/troubleshooting/installation_troubleshooting.md index 98e1fe09..b6c5813f 100644 --- a/_docs/developer/troubleshooting/installation_troubleshooting.md +++ b/_docs/developer/troubleshooting/installation_troubleshooting.md @@ -293,9 +293,29 @@ ___ ## Troubleshooting Pre-Packaged VM -Some issues with the pre-packaged VM can be fixed by installing a different version. Once you've installed a pre-packaged VM, it does not recieve version updates, so it can also be a good idea to update the pre-packaged version periodically. To see your current VM version, run `vagrant up` and look at the output. You should see something like `==> ubuntu-22.04: Checking if box 'SubmittyBot/ubuntu22-dev' version '26.06.00.2606070357' is up to date...`. In this case `26.06.00.2606070357` is the version number. +Some issues with the pre-packaged VM can be fixed by installing a different version. Once you've installed a pre-packaged VM, it does not recieve version updates, so it can also be a good idea to update the pre-packaged version periodically. To see your current VM version, run `vagrant box list` and look at the output. You should see something like `SubmittyBot/ubuntu22-dev (virtualbox, 26.06.00.2606070357, (amd64))`. In this case, `26.06.00.2606070357` is the version number. -### Instructions for Changing the Pre-Packaged VM Version +You may also see multiple versions of the VM. If you want to know what version the VM is using when you run `vagrant up`, follow these steps: + +1. Run `vagrant up` and look at the output. +2. You should see something like `==> ubuntu-22.04: Checking if box 'SubmittyBot/ubuntu22-dev' version '26.06.00.2606070357' is up to date...`. + +In this case, `26.06.00.2606070357` is the version number. + +If you have multiple versions of the VM, you can also run `vagrant box prune` to remove the old versions. + +### Instructions for Updating the Pre-Packaged VM Version +From your main Submitty repository, e.g. `/GIT_CHECKOUT/Submitty/`, run: + +``` +vagrant box update +``` + +This will download the newest version of the VM. It will take approximately 30 minutes to download. + +### Instructions for Specifying the Pre-Packaged VM Version + +These steps may be useful if you wish to roll your VM back or to upgrade to an intermediate version. From your main Submitty repository, e.g. `/GIT_CHECKOUT/Submitty/`, run: @@ -307,7 +327,7 @@ This will destroy your current VM and reset the Vagrant environment. *Note: If you have more than one VM (perhaps by accident), you can see a list of VMs with the command* `vagrant global-status`. *VMs listed will be given a unique id. You can then run* `vagrant destroy 1a2b3c4d`. *Replace* `1a2b3c4d` *with the id of the VM you wish to destroy.* -on Linux/MacOS, type: +Then, on Linux/MacOS, type: ``` PREBUILT_VERSION={version} vagrant up --provider=virtualbox ``` @@ -322,4 +342,4 @@ If you are importing a new version, it will take approximately 30 minutes to dow *The version must be only the numbers, not including the* `v` *in front, for example* `26.06.00.2606070357` *not* `v26.06.00.2606070357`. -*Note: You can find pre-packaged Submitty VM versions on the [Hashicorp Vagrant Box Catalog](https://portal.cloud.hashicorp.com/vagrant/discover/SubmittyBot/ubuntu22-dev) by navigating to the 'Versions' tab in the sidebar. Make sure to follow the [Submitty installation instructions](/developer/getting_started/vm_install_using_vagrant) when setting up your development environment.* +*Note: You can find pre-packaged Submitty VM versions on the [Hashicorp Vagrant Box Catalog](https://portal.cloud.hashicorp.com/vagrant/discover/SubmittyBot/ubuntu22-dev) by navigating to the 'Versions' tab in the sidebar. Make sure to follow the [Submitty installation instructions](/developer/getting_started/vm_install_using_vagrant) when setting up your development environment. A complete list of Vagrant commands can be found here: [Hashicorp Vagrant CLI Docs](https://developer.hashicorp.com/vagrant/docs/cli).* From 5dccd21074b2fe13500952209d859d820ef85891 Mon Sep 17 00:00:00 2001 From: roye2 <07eeroy@gmail.com> Date: Wed, 10 Jun 2026 12:34:15 -0400 Subject: [PATCH 6/6] minor wording corrections --- .../developer/troubleshooting/installation_troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_docs/developer/troubleshooting/installation_troubleshooting.md b/_docs/developer/troubleshooting/installation_troubleshooting.md index b6c5813f..b17f51e6 100644 --- a/_docs/developer/troubleshooting/installation_troubleshooting.md +++ b/_docs/developer/troubleshooting/installation_troubleshooting.md @@ -295,7 +295,7 @@ ___ Some issues with the pre-packaged VM can be fixed by installing a different version. Once you've installed a pre-packaged VM, it does not recieve version updates, so it can also be a good idea to update the pre-packaged version periodically. To see your current VM version, run `vagrant box list` and look at the output. You should see something like `SubmittyBot/ubuntu22-dev (virtualbox, 26.06.00.2606070357, (amd64))`. In this case, `26.06.00.2606070357` is the version number. -You may also see multiple versions of the VM. If you want to know what version the VM is using when you run `vagrant up`, follow these steps: +After running `vagrant box list`, you may see multiple versions of the VM. If you want to know what version the VM is using when you run `vagrant up`, follow these steps: 1. Run `vagrant up` and look at the output. 2. You should see something like `==> ubuntu-22.04: Checking if box 'SubmittyBot/ubuntu22-dev' version '26.06.00.2606070357' is up to date...`. @@ -315,7 +315,7 @@ This will download the newest version of the VM. It will take approximately 30 m ### Instructions for Specifying the Pre-Packaged VM Version -These steps may be useful if you wish to roll your VM back or to upgrade to an intermediate version. +These steps may be useful if you wish to roll your VM back or to upgrade to a version besides the newest available. From your main Submitty repository, e.g. `/GIT_CHECKOUT/Submitty/`, run: