Thanks for your quick and helpful response.
On Fri, Feb 26, 2021 at 9:31 AM Emmanuel Kasper <firstname.lastname@example.org
> 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 ?
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
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:
Please let me know if it needs to be made in a different way / or the
idea is not useful at all ;)
> Also are you sure you're using NFS inside the box, did you configure
> that manually, as the default filesharing mechanism for VirtualBox
> vagrant boxes is vboxsf.
> You can check with
> grep work /proc/mounts
> what is the shared folder mechanism you're using.
Sorry, my fault!
These machines use vboxsf.
I somehow wrongly remembered that the synced folder that is not
rsynced is nfs, or had it like that in another setup some time
but when writing nfs above I just assumed that and didn't really check.
And it was actually not part of my expected result, because I only
wanted the files available and shared with the host.
> Last question, what is your host system ?
It's Ubuntu 20.10.
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.
But that's another topic...