hi erik

your vagrant example run in my box here

can explain about the docker inside vagrant

guest.vm.provider "docker" do |docker, override|
      docker.image = "ubuntu"
      docker.name = "guest"
      docker.expose = [22]
      docker.has_ssh = true
      docker.remains_running = true
      docker.vagrant_machine = "host"
      docker.vagrant_vagrantfile = "Vagrantfile"
    end


how to try it?


--
Frans Thamura (曽志胜)
Shadow Master and Lead Investor
Meruvian.
Integrated Hypermedia Java Solution Provider.

Mobile: +628557888699
Blog: http://blogs.mervpolis.com/roller/flatburger (id)

FB: http://www.facebook.com/meruvian
TW: http://www.twitter.com/meruvian / @meruvian
Website: http://www.meruvian.org

"We grow because we share the same belief."


On Sun, Aug 17, 2014 at 9:34 PM, Erik Stephens <[email protected]> wrote:
> Thanks for the reply.  I'm running on a Mac.  I prefer not to have to run
> Vagrant on the remote machine.  I want to be able to use my workstation as a
> kind of Puppet master, mainly because I'm working with heterogenous
> configuration mgmt (Bash, Puppet, Chef, Ansible) and heterogenous
> infrastructure (VirtualBox, Rackspace, AWS, leased HW).
>
> Is that pushing the boundaries of what Vagrant was intended to do?
> Terraform looks to be a good fit for this use case but it's so new.  I want
> developers and operations to have the flexibility to provision wherever they
> prefer.  Does this fit anyone else's requirements?  If so, how are you
> tackling it?
>
> Here's the crux of my Vagrantfile:
> """
>   config.vm.define "host" do |host|
>     host.vm.box = "dummy"
>     host.vm.provider :managed do |managed, override|
>       managed.server = "my.server.net"
>       override.ssh.username = "me"
>       override.ssh.private_key_path = "~/.ssh/me.pem"
>     end
>   end
>
>   config.vm.define "guest" do |guest|
>     guest.vm.provider "docker" do |docker, override|
>       docker.image = "ubuntu"
>       docker.name = "guest"
>       docker.expose = [22]
>       docker.has_ssh = true
>       docker.remains_running = true
>       docker.vagrant_machine = "host"
>       docker.vagrant_vagrantfile = "Vagrantfile"
>     end
>   end
> """
>
> Thank you,
> Erik
>
> On Aug 16, 2014, at 8:26 PM, Alvaro Miranda Aguilera <[email protected]>
> wrote:
>
> whats the os where you are running vagrant?
>
> if linux or mac, you can install docker binary and set the variables for
> remote docker.
>
> but, if the host is not linux or mac, then the best will be run vagrant from
> the box over ssh
>
> as i see it, vagrant is meant primarily to be used on the local machine..
> and some plugins allow remote boxes, but you want something different from
> what i see
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to