5:39 a.m.
Hullo
I keep falling foul of this, so I may well have raised a bug about it in the past, but I
cannot fathom where/how now.
I use fedora images with virtualbox/vagrant, and I try to standardise on the fedoraproject
images (https://bit.ly/2Znj8h1). A feature of these images is that they tend to enable
rsync base synchronisation of the host working directory and the guest `/vagrant`
directory with the following line in, eg,
`~/.vagrant.d/boxes/fedora-VAGRANTSLASH-32-cloud-base/32.20200422.0/virtualbox/Vagrantfile`:
```
config.vm.synced_folder ".", "/vagrant", type: "rsync"
```
I don’t think that it’s my setup specifically, which uses the vagrant plugin
`vagrant-vbguest`, but that line breaks the synchronisation between the guest and the host
directories, other than with an explicit `vagrant rsync` (from host to guest).
Removing the line improves the experience of using the images hugely ;-)
Tim
11:41 a.m.
On Fri, Sep 11, 2020 at 6:40 AM Tim Coote
<tim+fedoraproject.org(a)coote.org> wrote:
Hullo
I keep falling foul of this, so I may well have raised a bug about it in the past, but I
cannot fathom where/how now.
I use fedora images with virtualbox/vagrant, and I try to standardise on the
fedoraproject images (https://bit.ly/2Znj8h1). A feature of these images is that they tend
to enable rsync base synchronisation of the host working directory and the guest
`/vagrant` directory with the following line in, eg,
`~/.vagrant.d/boxes/fedora-VAGRANTSLASH-32-cloud-base/32.20200422.0/virtualbox/Vagrantfile`:
```
config.vm.synced_folder ".", "/vagrant", type: "rsync"
```
I don’t think that it’s my setup specifically, which uses the vagrant plugin
`vagrant-vbguest`, but that line breaks the synchronisation between the guest and the host
directories, other than with an explicit `vagrant rsync` (from host to guest).
Removing the line improves the experience of using the images hugely ;-)
I am pretty sure we put that in so that it would work properly with
"homes that were not at home" (e.g. /var/home on silverblue) and/or to
not cause unexpected user behavior with defaulting to rsync vs a
"proper" mount. In other words, at this point, it might make sense to
remove this from the vagrant image definition.
However, you could also fix this for your local by making your
$VAGRANT_HOME/Vagrantfile do something special if it detects a
/vagrant for the user home. I am not sure exactly how you would want
to do it (as I don't know why vbguest breaks) but you could override
the boxes Vagrantfile with like config.vm.synced_folder ".",
"/home/vagrant", type: "rsync" or something. If you didn't
already
know, Vagrantfiles are additive and can be overridden (see
https://www.vagrantup.com/docs/vagrantfile for more details).
Unfortunately, I don't know how/where these are being maintained
anymore so I can't answer the "real" question of where to report the
issue.
langdon
>
> Tim
> _______________________________________________
> cloud mailing list -- cloud(a)lists.fedoraproject.org
> To unsubscribe send an email to cloud-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
1312
days inactive
1316
days old
1 comments
2 participants
participants (2)
-
Langdon White -
Tim Coote