Solucionado (ver solução)
Solucionado
(ver solução)
1
resposta

Erro na hora de subir a VM (Vbox 6.0.4)

Elder@SRV-01 MINGW64 /d/ambiente_dev_apresentação/bionIC $ Vagrant up ==> vagrant: A new version of Vagrant is available: 2.2.16 (installed version: 2.2.3)! ==> vagrant: To upgrade visit: https://www.vagrantup.com/downloads.html

C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/json/common.rb:156:in initialize': negative string size (or size too big) (ArgumentError) from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/json/common.rb:156:innew' from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/json/common.rb:156:in parse' from C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/json/common.rb:335:inload' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine_index.rb:293:in unlocked_reload' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine_index.rb:53:inblock in initialize' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine_index.rb:323:in block in with_index_lock' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine_index.rb:321:inopen' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine_index.rb:321:in with_index_lock' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/machine_index.rb:52:ininitialize' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/environment.rb:724:in new' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/environment.rb:724:inmachine_index' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/environment.rb:208:in block in action_runner' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/action/runner.rb:33:inrun' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/environment.rb:526:in hook' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/environment.rb:775:inunload' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/bin/vagrant:185:in ensure in <main>' from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/bin/vagrant:185:in

'

1 resposta
solução!

Resolvido:

  • Realizado a desinstalação do vagrant

pasta excluídas:

  • .vagrant (c:\users\Elder
  • .vagrant.d (c:\users\Elder
  • .VirtualBox.d (c:\users\Elder
  • Vagrantfile (c:\users\Elder

Realizado a reinstalação do Vagrant version 2.2.3

Bringing machine 'default' up with 'virtualbox' provider... ==> default: Box 'ubuntu/bionic64' could not be found. Attempting to find and install... default: Box Provider: virtualbox default: Box Version: >= 0 ==> default: Loading metadata for box 'ubuntu/bionic64' default: URL: https://vagrantcloud.com/ubuntu/bionic64 ==> default: Adding box 'ubuntu/bionic64' (v20210415.0.0) for provider: virtualbox default: Downloading: https://vagrantcloud.com/ubuntu/boxes/bionic64/versions/20210415.0.0/providers/virtualbox.box default: Download redirected to host: cloud-images.ubuntu.com default: ==> default: Successfully added box 'ubuntu/bionic64' (v20210415.0.0) for 'virtualbox'! ==> default: Importing base box 'ubuntu/bionic64'... ==> default: Matching MAC address for NAT networking... ==> default: Checking if box 'ubuntu/bionic64' version '20210415.0.0' is up to date... ==> default: Setting the name of the VM: bionc2_default_1619978567876_57802 Vagrant is currently configured to create VirtualBox synced folders with the SharedFoldersEnableSymlinksCreate option enabled. If the Vagrant guest is not trusted, you may want to disable this option. For more information on this option, please refer to the VirtualBox manual:

https://www.virtualbox.org/manual/ch04.html#sharedfolders

This option can be disabled globally with an environment variable: