Library error when loading the latest Ubuntu/Jammy64 box image

[Gary Cartagena]

I am using Vagrant to build a new Ubuntu/Jammy64 virtual machine.
When I last built this box, (version: '20221014.0.0') there were no issues.
However, when I tried to build a new box with the latest version I got library errors. See the following output for the steps.

--- BEGIN STDOUT ---
PS D:\Source\vm-box> vagrant up

Bringing machine 'devbx' up with 'virtualbox' provider...
==> devbx: Importing base box 'ubuntu/jammy64'...
==> devbx: Matching MAC address for NAT networking...
==> devbx: Checking if box 'ubuntu/jammy64' version '20221124.0.0' is up to date...
==> devbx: [vagrant-hostsupdater] Checking for host entries
==> devbx: [vagrant-hostsupdater] Writing the following entries to (C:/windows/system32/drivers/etc/hosts)
==> devbx: [vagrant-hostsupdater] 192.168.xxx.xxx devbox.local # VAGRANT: 0cc7a78453059619464db1a31e5d3c72 (devbx) / a45db966-6006-415a-9304-5fd788c0ff81
==> devbx: [vagrant-hostsupdater] 192.168.xxx.xxx api.devbox.local, tekdev.local # VAGRANT: 0cc7a78453059619464db1a31e5d3c72 (devbx) / a45db966-6006-415a-9304-5fd788c0ff81
==> devbx: Setting the name of the VM: v-pods_devbx_1669847163850_26465
==> devbx: Clearing any previously set network interfaces...
==> devbx: Preparing network interfaces based on configuration...
    devbx: Adapter 1: nat
    devbx: Adapter 2: hostonly
==> devbx: Forwarding ports...
    devbx: 22 (guest) => 2222 (host) (adapter 1)
==> devbx: Running 'pre-boot' VM customizations...
==> devbx: Booting VM...
==> devbx: Waiting for machine to boot. This may take a few minutes...
    devbx: SSH address: 127.0.0.1:2222
    devbx: SSH username: vagrant
    devbx: SSH auth method: private key
==> devbx: Machine booted and ready!
[devbx] A Virtualbox Guest Additions installation was found but no tools to rebuild or start them.
Reading package lists...
Building dependency tree...
Reading state information...
linux-headers-5.15.0-53-generic is already the newest version (5.15.0-53.59).
linux-headers-5.15.0-53-generic set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 dkms : Depends: gcc-12 but it is not installable
        Recommends: fakeroot but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
... ... ...
--- END STDOUT ---

At this point I killed the vagrant build. I don't need to build a box with library errors since I can revert to the old version.

Thank you for your attention.

G...C

[John Chittum (jchittum)]

Could you provide information about how you're deploying the box and vagrant environment?

1. vagrant version
2. virtualbox version
3. any deployment info / scripts you can share

it looks like you're automation, and I need to be able to reproduce what's happening. Looking at the error, it looks more likely to be at the package level than vagrant level

[Gary Cartagena (unkulmunki)]

Running On Windows 10 w/ default PowerShell
VirtualBox v. 6.1.36 r152435
Vagrant v. 2.2.19
Vagrant Plugins:
  vagrant-hostmanager (1.8.9, global)
    - Version Constraint: > 0
  vagrant-hostsupdater (1.2.4, global)
    - Version Constraint: > 0
  vagrant-vbguest (0.30.0, global)
    - Version Constraint: > 0

I have attached the Vagrantfile and Hosts file.

I do not think this is specific to the package, since it is not getting to the provisioning step at all.
Actually, it looks like this error is failing while trying to install the VB-Guest libraries which is triggered by the vagrant plugin and which is BEFORE the provision script.

Here is the key section:
  [devbx] A Virtualbox Guest Additions installation was found but no tools to rebuild or start them.

So, it might be an incompatibility with VB-Guest and the latest version...

Thanks for looking into this.

---
Gary Cartagena
Technical Consultant – Tek Management LLC.
• Work: <email address hidden>
• Voice: [phone]

-----Original Message-----
From: <email address hidden> <email address hidden> On Behalf Of John Chittum
Sent: Monday, December 5, 2022 9:16 AM
To: <email address hidden>
Subject: [Bug 1998399] Re: Library error when loading the latest Ubuntu/Jammy64 box image

Could you provide information about how you're deploying the box and vagrant environment?

1. vagrant version
2. virtualbox version
3. any deployment info / scripts you can share

it looks like you're automation, and I need to be able to reproduce what's happening. Looking at the error, it looks more likely to be at the package level than vagrant level

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1998399

Title:
  Library error when loading the latest Ubuntu/Jammy64 box image

Status in cloud-images:
  New

Bug description:
  I am using Vagrant to build a new Ubuntu/Jammy64 virtual machine.
  When I last built this box, (version: '20221014.0.0') there were no issues.
  However, when I tried to build a new box with the latest version I got library errors. See the following output for the steps.

  --- BEGIN STDOUT ---
  PS D:\Source\vm-box> vagrant up

  Bringing machine 'devbx' up with 'virtualbox' provider...
  ==> devbx: Importing base box 'ubuntu/jammy64'...
  ==> devbx: Matching MAC address for NAT networking...
  ==> devbx: Checking if box 'ubuntu/jammy64' version '20221124.0.0' is up to date...
  ==> devbx: [vagrant-hostsupdater] Checking for host entries
  ==> devbx: [vagrant-hostsupdater] Writing the following entries to (C:/windows/system32/drivers/etc/hosts)
  ==> devbx: [vagrant-hostsupdater] 192.168.xxx.xxx devbox.local # VAGRANT: 0cc7a78453059619464db1a31e5d3c72 (devbx) / a45db966-6006-415a-9304-5fd788c0ff81
  ==> devbx: [vagrant-hostsupdater] 192.168.xxx.xxx api.devbox.local, tekdev.local # VAGRANT: 0cc7a78453059619464db1a31e5d3c72 (devbx) / a45db966-6006-415a-9304-5fd788c0ff81
  ==> devbx: Setting the name of the VM: v-pods_devbx_1669847163850_26465
  ==> devbx: Clearing any previously set network interfaces...
  ==> devbx: Preparing network interfaces based on configuration...
      devbx: Adapter 1: nat
      devbx: Adapt...