best will be build a box fit to your own use

you can use
https://www.packer.io/

you can find templates here:
https://github.com/chef/bento

alvaro


On Mon, Jan 27, 2020 at 1:14 AM Matthew Pounsett <[email protected]> wrote:

>
> I'm using VirtualBox 6.0.14, Vagrant 2.2.6 with the vagrant-vbguest 0.23.0
> plugin.  I'm trying to get a Debian Buster box working, but I'm having huge
> problems with the guest plugins.
>
> Using the 'debian/buster64' box, the guest plugin install fails because
> the box is out of date compared to the buster packages actually available
> online (10.0.0 vs. 10.2)
>
> E: Unable to locate package linux-headers-4.19.0-5-amd64
> E: Couldn't find any package by glob 'linux-headers-4.19.0-5-amd64'
> E: Couldn't find any package by regex 'linux-headers-4.19.0-5-amd64'
>
> Using the 'generic/debian10' box, I run into a problem where the box
> already has the VirtualBox 5.1.38 guest additions installed, and
> vagrant-vbguest appears to succeed in updating them, but the default
> /vagrant shared folder fails to mount.  A couple of potential errors pop up
> during the upgrade:
>
> Removing installed version 5.1.38 of VirtualBox Guest Additions...
> ./install.sh: 143: ./install.sh: VBoxControl: not found
> This system appears to have a version of the VirtualBox Guest Additions
> already installed.  If it is part of the operating system and kept
> up-to-date,
> there is most likely no need to replace it.  If it is not up-to-date, you
> should get a notification when you start the system.  If you wish to
> replace
> it with this version, please do not continue with this installation now,
> but
> instead remove the current version first, following the instructions for
> the
> operating system.
>
> If your system simply has the remains of a version of the Additions you
> could
> not remove you should probably continue now, and these will be removed
> during
> installation.
>
> Do you wish to continue? [yes or no]
> touch: cannot touch '/var/lib/VBoxGuestAdditions/skip-4.19.0-6-amd64': No
> such file or directory
> Copying additional installer modules ...
>
>
> And later in my provisioning script:
>
> vm01: ls: cannot access '/vagrant': No such file or directory
>
>
> If I halt and restart the VMs, they appear to boot with the correct
> GuestAdditions, but I still don't get the /vagrant shared folder.
>
> [vm01] GuestAdditions 6.0.14 running --- OK.
>
>
>  I'm not sure what to poke at here to fix this.
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/4576d093-6e15-4c9a-974d-862cb9c0c8b7%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/4576d093-6e15-4c9a-974d-862cb9c0c8b7%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0exmTDru0-Ugc73OhD8kpaWif%3D5tYNkDPpJYqOqGy5xC2g%40mail.gmail.com.

Reply via email to