docker fails with ~/.vagrant.d/boxes file exists, if boxes are symlinked somewhere else

[thigg]

Describe the bug
I got a symlink from .vagrant.d/boxes to another disk. This lets the example from the readme fail with:

/opt/vagrant/embedded/lib/ruby/2.7.0/fileutils.rb:250:in `mkdir': File exists @ dir_s_mkdir - /.vagrant.d/boxes (Errno::EEXIST)

To Reproduce
Steps to reproduce the behavior:

1. symlink .vagrant.d/boxes somewhere else
2. run

docker run -it --rm \
  -e LIBVIRT_DEFAULT_URI \
  -v /var/run/libvirt/:/var/run/libvirt/ \
  -v ~/.vagrant.d:/.vagrant.d \
  -v $(realpath "${PWD}"):${PWD} \
  -w "${PWD}" \
  --network host \
  vagrantlibvirt/vagrant-libvirt:latest \
    vagrant status

Expected behavior
Works

Screenshots

Versions (please complete the following information)::

• Libvirt version: 9.2.0
• Vagrant version [output of vagrant version]: 2.3.4
• Vagrant flavour [Upstream or Distro]: distro (arch)
• Vagrant plugins versions (including vagrant-libvirt) [output of vagrant plugin list]:

Debug Log
shouldn't matter

A Vagrantfile to reproduce the issue:
shouldn't matter

[electrofelix]

If you symlink the boxes folder elsewhere then you will need to modify the docker command to add a volume mount for the other path and mount it into the image under the expected path as well, there isn't any way around this.

The only solution to this is to provide a more complex script that checks the entire contents of ~/.vagrant.d and also mounts in any symlinked paths recursively.