Closed StefanScherer closed 10 years ago
Hi @StefanScherer,
Yes very good observation, I think we should add this to our documentation in the Wiki. I'll flag it as invalid and close this as it's not inherent to vagrant-vcloud but more as a default value in vagrant.
I will add your solution into the vagrant-vcloud wiki.
Today, I encountered a problem with port forwardings. Using more and more vApps in parallel, one box could not be created correctly, even after a
vagrant destroy -f spooler3
andvagrant up spooler3
.The debug log showed me
Always problem after port 2250. So I went down into the vagrant sources and found it.
It is also mentioned in the Vagrant docs, so it is worth mentioning to increase
config.vm.usable_port_range
to more than2200..2250
.The default port range ist 2200..2250 and will be too small using vCloud very fast. Probably we should handle that situation better than crashing.
So others might find these lines useful in a global Vagrantfile: