Vagrant Setup - Resolving port conflicts on Mac

[benburg7]

Hello,

Apologies if this question was answered on another thread, but I did not see a response that I was able to use to fix my issue.

After running the "vagrant up --no-parallel" command, I receive the error below (I'm on a mac). I tried following the steps in the "How do I resolve any port conflicts?" section in appendix A, but after that I would just get a time out error whenever trying to run vagrant up --no-parallel. Did anyone else run into this problem and find a solution? Does anyone have an example of what the vagrantfile.dockerhost file should look like after adding the custom port statements? I'm thinking maybe I added those statements to the wrong place within the file?

Thanks,
Ben

Error message:
"Vagrant cannot forward the specified ports on this VM, since they
would collide with some other application that is already listening

on these ports. The forwarded port to 9312 is already in use

on the host machine.

To fix this, modify your current project's Vagrantfile to use another

port. Example, where '1234' would be replaced by a unique host port:

config.vm.network :forwarded_port, guest: 9312, host: 1234

Sometimes, Vagrant will attempt to auto-correct this for you. In this

case, Vagrant was unable to. This is usually because the guest machine

is in a state which doesn't allow modifying port forwarding. You could

try 'vagrant reload' (equivalent of running a halt followed by an up)

so vagrant can attempt to auto-correct this upon booting. Be warned

that any unsaved work might be lost."

[Foxtrod89]

Did you follow this?
I got same issue with vagrant machine on BigSur 11.6
Or https://github.com/scalingexcellence/scrapybook-2nd-edition.git, use this updated repo, you dont even need setup local env to run tests as it hosted on aws