Skip to content

Commit b93445a

Browse files
authored
Fix ambiguous name of the Vagrant VM in the exercise instructions
Closes #237
1 parent fbb334f commit b93445a

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

02_virtualization_and_containers/virtualmachines_containers_exercise.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -211,7 +211,7 @@ Fork and clone the repository mentioned above. The repository initially contains
211211
212212
- We want to start from scratch so initialize a new box using `vagrant init` inside this repository and add the resulting `Vagrantfile` to Git. Then adapt your `Vagrantfile` to incorporate the following settings:
213213
- Your virtual machine should be based on the [`bento/ubuntu-24.04` image](https://portal.cloud.hashicorp.com/vagrant/discover/bento/ubuntu-24.04). In case you need a different provider (e.g., `libvirt`), feel free to use another box, but state this in your submission.
214-
- The name of your VM should be `USERNAME-vm`.
214+
- The name of your VM should be `USERNAME-vm-vagrant`.
215215
- The VM must request [1024 MB of main memory](https://developer.hashicorp.com/vagrant/docs/providers/virtualbox/configuration).
216216
- We want a [new shared folder](https://developer.hashicorp.com/vagrant/docs/synced-folders/basic_usage) in our virtual machine. The directory where the `Vagrantfile` resides, i.e. `.`, should be mounted by default as `/mnt/shared/` in your virtual machine.
217217
- Run your box with `vagrant up` and make sure that everything works out as expected (`vagrant ssh`). If everything is fine, you can `exit` the VM. You do **not** have to stop/destroy the VM for the next step.

0 commit comments

Comments
 (0)