I went into more detail in the other thread, but the docker compose
provisioner just uses docker compose to run docker commands, so I suspect
it's demonstrating a vagrant edge case (sometimes-faulty identification of
the private network's interface).
On Tue, Mar 13, 2018, 3:58 AM Alvaro Miranda Ag
Maybe its a bug in the vagrant-docker-compose plugin ?
It seems to me you have isolated from where the problem is coming from..
On Mon, Mar 12, 2018 at 2:44 PM, Jamie Jackson wrote:
> FYI, I added a repro case to the ticket (https://github.com/hashicorp/
> vagrant/issues/9546). Downgrading to
FYI, I added a repro case to the ticket (https://github.com/hashicorp/
vagrant/issues/9546). Downgrading to Vagrant 1.8.x is the only workaround I
know of, so please let me know if you can think of any workaround that
could keep me on a more current version.
On Thu, Mar 8, 2018 at 4:59 PM, Jamie J
I've copied the contents to https://github.com/hashicorp/vagrant/issues/9546,
so go ahead and delete my comments. I'll try to get a repro case together.
On Thu, Mar 8, 2018 at 1:03 PM, Alvaro Miranda Aguilera
wrote:
> not sure if the same
>
> please open a new issue, include a repro case and ins
not sure if the same
please open a new issue, include a repro case and instructions how to repro
please @kikitux so i can get the notification to look into
if happens to you and more people, should happen to us
if you are ok, i would like to the delete the comment in that issue in 9510
since w
