Fix synced folders when running docker-run after vagrant up

I believe this fixes the problem in #3873, not sure why the host_sfid is used (appears to randomly generate), instead I would think we should check if that same mount path was already used in the host VM, and if so, reuse it (instead of trying to remount a new path, which doesn't work because it isn't being mounted on the host VM).
Unfortunately this won't work because the provider can be any class (Hyper-V, AWS, etc.) and they aren't required to have a `driver`.