A tramp is using a different host machine

Question

I want to use Vagrant, but not to pollute my machine, with which I work with n + VirtualBox machines.

I searched the Internet but found nothing. I really want to work with my laptop and call vagrant up there, but it should start the guest on another one, for example. Linux on my network where VirtualBox is installed.

Is this possible at this time because it is not much different from the aws provider who does just that with EC2.

It would be nice if he used NTFS instead of aws-provider , which uses rsync.

Thanks for your answers in advance. Daniel

Answer 1

Since the tramp does not support this directly, I would do something like this.

First, save all your Vagrantfiles in subdirectories of the same directory on the host server. Then create a vagrant_runner script on your main machine, looking something like this:

 #!/bin/bash VAGRANT_HOME='/home/bar/vagrant' cd ${VAGRANT_HOME}/$1 # Strip off the subdir name so we can pass all the rest of our # arguments to vagrant shift vagrant $@ 

Then on your laptop you will have an rvagrant script:

 #!/bin/bash VAGRANT_HOST=dnsname_of_vagrant_host VAGRANT_USER=vagrant_user ssh ${VAGRANT_USER}@${VAGRANT_HOST} vagrant_runner $@ 

You can then do rvagrant foo up to start the vms defined in / home / bar / vagrant / foo / Vagrantfile, or rvagrant foo destroy -f to destroy it.

Answer 2

This is currently not possible. GitHub had an issue , but it was closed. In the comments, the author says:

This is something that I’m not even going to look at creating Vagrant itself, at least until the publication of 1.0 :) I marked this as a function request, but I do not plan to look at it again a bit, if there are urgent good reasons.

About a year later, and then about two months ago, two people asked about the status of this problem, since now we are publishing 1.0, but so far there has been no reaction to this, unfortunately: - (