4 ms·
Default value is 300 seconds: https://developer.hashicorp.com/vagrant/docs/vagrantfile/machine_settings https://developer.hashicorp.com/vagrant/docs/vagrantfile
by raincom 3y ago
Default value is 300 seconds: https://developer.hashicorp.com/vagrant/docs/vagrantfile/machine_settings https://developer.hashicorp.com/vagrant/docs/vagrantfile/mac...
So, just set config.vm.boot_timeout to 900 in the vagrant file, and see what happens.
- tromp 3y agoRe-running vagrant up gives Bringing machine 'default' up with 'virtualbox' provider... ==> default: Checking if box 'debian/bookworm64' version '12.20240212.1' is up to date... ==> default: Machine 'default' has a post `vagrant up` message. This is a message ==> default: from the creator of the Vagrantfile, and not from Vagrant itself: ==> default: ==> default: Vanilla Debian box. See https://app.vagrantup.com/debian for help and bug reports almost immediately. Looks like timing out was not the real issue. I can run vagrant ssh now. Realizing there's no cc and no git, I try $ apt-get update Reading package lists... Done E: List directory /var/lib/apt/lists/partial is missing. - Acquire (13: Permission denied) Hmm, still some challenges ahead...