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

Bug#983551: 983551: cloud.debian.org: Vagrant/Virtualbox image testing64 ownership of synced_folders is always root

On 3/2/21 10:03 PM, Henning Sprang wrote:

Hi Emmanuel,

Thanks for your quick and helpful response.

On Fri, Feb 26, 2021 at 9:31 AM Emmanuel Kasper <manu@debian.org <mailto:manu@debian.org>> wrote:
 > ...
 > Actually, you don't need anymore the vagrant-vbguest pluging for testing
 > boxes, as all drivers are now in the main debian kernel. Can you try to
 > destroy the box, and recreate the boxes without the vagrant-vbguest
 > plugin to see if that helps ?

Yes, great!

Disabling vbguest with

config.vbguest.auto_update = false

disables it for the current Vagrantfile without removing the plugin
globally, and then after destroying and restarting the machine (I
didn't try to fiddle with removing what vbguest installed before,
it might work for others who dont want to reinstall) things work as
expected, the owner of the synced folder is vagrant again.

I didn't come up with trying to see what happened without vbguest /
guest additions at all, because every setup I worked with until now
needed them.
I wonder if there is a good way to warn other people running into the
same situation doing the guest install as they are used to forever,
either manual or with the vbguest plugin.

Maybe it could be mentioned in the notes for the image on vagrant hub
maybe, or in the "post vagrant up" message that appears at the end of

I made a proposal for this:
https://salsa.debian.org/cloud-team/vagrant-boxes/-/merge_requests/6 <https://salsa.debian.org/cloud-team/vagrant-boxes/-/merge_requests/6>

Please let me know if it needs to be made in a different way / or the
idea is not useful at all ;)

Thanks for the idea, actually mentioning that in the vbguest-plugin on each boot is a bit overkill, so I will create a FAQ on the Debian Wiki
and link it from http://app.vagrantup.com/debian,
since that plugin is the number one concern people have with their boxes.

I also realized that virtualbox is not in testing, and the package has
quite a list of open, in part old bugs,
is this the time to migrate to another virtualization backend with vagrant?
Only, last time I tried with another backend(dont remember which, the
next lxc?) it was not running so smooth.

The main advantage of Virtualbox is that it's multiplatform. Otherwise I would recommend libvirt, the virtualization is a tad faster.

It used to be that VirtualBoxes VM crashed when the host system went into sleep mode, but this does not happen anymore with the Debian Testing / Debian 11.


Reply to: