[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

'vagrant up' does not seem to properly start 'debian/bookworm64'



Hello,

my host machine is x86_64 with Ubuntu 22.04.2 LTS and I am using Vagrant 2.2.9 (from Ubuntu APT reposiotory).

I did not have any issue the VM box 'debian/bullseye64' but when replacing 'debian/bullseye64' by 'debian/bookworm64' I have the error 'Warning: Authentication failure. Retrying...'


More information here.

1. My Vagrantfile for 'debian/bullseye64'

Vagrant.configure("2") do |config|
  config.vm.box = "debian/bullseye64"
end

2. When I do 'vagrant up' for this Vagrantfile:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'debian/bullseye64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'debian/bullseye64' version '11.20230615.1' is up to date... ==> default: Setting the name of the VM: test_debian_default_1690396203042_94774
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of     default: VirtualBox! In most cases this is fine, but in rare cases it can     default: prevent things such as shared folders from working properly. If you see     default: shared folder errors, please make sure the guest additions within the     default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 6.0.0 r127566
    default: VirtualBox Version: 6.1
==> default: Mounting shared folders...
    default: /vagrant => /tmp/test_debian

==> 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


3. When I replace 'debian/bullseye64' by 'debian/bookworm64' in Vagrantfile:

Vagrant.configure("2") do |config|
  config.vm.box = "debian/bookworm64"
end

4. And I do 'vagrant up' (after deleting the folder '.vagrant'):

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'debian/bookworm64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'debian/bookworm64' version '12.20230723.1' is up to date... ==> default: Setting the name of the VM: test_debian_default_1690396546792_50324
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

5. I launched the two boxes ('debian/bullseye64' and 'debian/bookworm64') with '--debug'. Here you can find the two logs for both boxes:

* debian/bullseye64 with --debug: https://drive.google.com/file/d/1soSxTuFVLtmpy75x2r1Idu1c0RM1UEAk/view?usp=drive_link

* debian/bookworm64 with --debug: https://drive.google.com/file/d/1AayMxzOi6NiCckkHTI8V7bl_DnnK8TlV/view?usp=drive_link





Reply to: