[vagrant-up] Re: Use box versioning without Vagrant Cloud?

Hi there Did you setup your custom Vagrant cloud using s3? I'm trying to do that and I'm looking resources related. El lunes, 19 de mayo de 2014, 1:29:19 (UTC-6), Ryan Parman escribió: > > I can't seem to find any documentation about leveraging Box Versioning > without Vagrant Cloud. My

Re: [vagrant-up] link to localhost using docker as provider

t inside one container is separate to the network in the other > container > > is like having 2 physical machines, and you want to access a remote > service. > could you explain a bit why you require localhost for a remote service ? > > > On Fri, Dec 2, 2016 at 1:38 AM, Eddy He

[vagrant-up] Re: link to localhost using docker as provider

I made a test and it seems that work well the following. link: "author:localhost" I don't like to add this configuration on each container, I would like to expose alway the service in the localhost. Any idea on how to do it? El jueves, 1 de diciembre de 2016, 18:38:02 (UTC-6), Eddy

[vagrant-up] link to localhost using docker as provider

Hi everyone Maybe you can help me to get this questions I'm using docker as a provider, I have two containers: *container1* and *service1* I need to reach the *service1:4505* from the *container1*, the docs says that is posible using link e.g. *"service1:service1*" but I would like to reach

[vagrant-up] Another way to create Vagrant boxes.

hi, I'm building custom vagrant boxes from boot2docker, is there a way to do it without using VirtualBox? probably is a newbie question, but I want to use containers to manage these creations, but VirtualBox not runs inside the container because VirtualBox is extremely host-dependent. Any