Entrar Ainda não tem acesso?
1
resposta

Vagrant up não funciona no Ubuntu 18.04.5 LTS

Referente ao curso Ansible: sua infraestrutura como código, no capítulo Primeiros passos com Ansible e atividade Mãos na massa: Começando com Ansible

por Rodrigo Bononi Garcia
| 15k xp | 4 posts
Analista

O comando Vagrant up não funciona no Ubuntu 18.04.5 LTS, apresenta a seguinte mensagem de erro:

Bringing machine 'wordpress' up with 'virtualbox' provider... ==> wordpress: Importing base box 'ubuntu/trusty64'... ==> wordpress: Matching MAC address for NAT networking... ==> wordpress: Checking if box 'ubuntu/trusty64' version '20190514.0.0' is up to date... ==> wordpress: Setting the name of the VM: wordpress_com_ansible_wordpress_1601958462464_65009 ==> wordpress: Clearing any previously set forwarded ports... ==> wordpress: Fixed port collision for 22 => 2222. Now on port 2202. ==> wordpress: Vagrant has detected a configuration issue which exposes a ==> wordpress: vulnerability with the installed version of VirtualBox. The ==> wordpress: current guest is configured to use an E1000 NIC type for a ==> wordpress: network adapter which is vulnerable in this version of VirtualBox. ==> wordpress: Ensure the guest is trusted to use this configuration or update ==> wordpress: the NIC type using one of the methods below: ==> wordpress: ==> wordpress: https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type ==> wordpress: https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type ==> wordpress: Clearing any previously set network interfaces... ==> wordpress: Preparing network interfaces based on configuration... wordpress: Adapter 1: nat wordpress: Adapter 2: hostonly ==> wordpress: Forwarding ports... wordpress: 22 (guest) => 2202 (host) (adapter 1) ==> wordpress: Running 'pre-boot' VM customizations... ==> wordpress: Booting VM... ==> wordpress: Waiting for machine to boot. This may take a few minutes... The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'poweroff' state. Please verify everything is configured properly and try again.

If the provider you're using has a GUI that comes with it, it is often helpful to open that and watch the machine, since the GUI often has more helpful error messages than Vagrant can retrieve. For example, if you're using VirtualBox, run vagrant up while the VirtualBox GUI is open.

The primary issue for this error is that the provider you're using is not properly configured. This is very rarely a Vagrant issue.

Após a mensagem de erro, acesso a console do VirtualBox e a VM está lá, criada. Se inicio a VM pela console ela carrega normalemente, o que pode ser?

1 resposta
por Jonilson Sousa
| 1554.4k xp | 2890 posts
Instrutor Software Developer at Alura Group

Olá Rodrigo, tudo bem? O erro em si é apresentado nesse trecho do log:

==>wordpress: Vagrant has detected a configuration issue which exposes a 
==> wordpress: vulnerability with the installed version of VirtualBox. The 
==> wordpress: current guest is configured to use an E1000 NIC type for a 
==> wordpress: network adapter which is vulnerable in this version of VirtualBox.

Onde ele indica que o Vagrant encontrou uma vulnerabilidade com a versão do VirtualBox que você está utilizando no momento. E no ainda indica que a máquina não está em um estado válido:

The guest machine entered an invalid state while waiting for it to boot.

Então você poderia verificar qual é a versão do seu VirtualBox e se possível atualizar para a versão 6 ou mais recente do VirtualBox? E depois tenta realizar o processo novamente e fala pra gente se deu certo!