From 14f447060894ba1bade046328f5f3851488243c6 Mon Sep 17 00:00:00 2001 From: Kilian Krampf Date: Wed, 30 Oct 2024 11:28:32 +0100 Subject: [PATCH] Add workaround hint for current Vagrant and VirtualBox versions --- .../virtualmachines_containers_exercise.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/02_virtualization_and_containers/virtualmachines_containers_exercise.md b/02_virtualization_and_containers/virtualmachines_containers_exercise.md index 835c666a..823f2781 100644 --- a/02_virtualization_and_containers/virtualmachines_containers_exercise.md +++ b/02_virtualization_and_containers/virtualmachines_containers_exercise.md @@ -35,6 +35,11 @@ Deadline: **Wednesday, November 13, 2024, 9:00** - Check in the VirtualBox manager that the VM is active. - Leave the SSH session (type `exit` and press `Enter` or use the shortcut `CTRL+D`) - Destroy the VM `vagrant destroy` +- **Additional note**: Currently (WT24/25) the latest versions of Vagrant (2.4.1) and VirtualBox (7.1) are incompatible. Either use an older version of VirtualBox (7.0) or use a workaround mentioned in [this Vagrant issue](https://github.com/hashicorp/vagrant/issues/13501). + - One workaround that is verified to work is to to modify the VirtualBox provider plugin and add a fake mapping to treat VirtualBox 7.1 like VirtualBox 7.0. + For further information look at [the original proposal of the workaround](https://github.com/hashicorp/vagrant/issues/13501#issuecomment-2389606077). + - Filepath for Windows: `C:\\Program Files\Vagrant\embedded\gems\gems\vagrant-2.4.1\plugins\providers\virtualbox\driver` + - Filepath for Linux:`/opt/vagrant/embedded/gems/gems/vagrant-2.4.1/plugins/providers/virtualbox/driver` #### Install Docker