subject:"Re\: \[vagrant\-up\] Private IP Assigned to Wrong NIC"

Re: [vagrant-up] Private IP Assigned to Wrong NIC

2018-03-13 Thread Jamie Jackson

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 Aguilera 
wrote:

> 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 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 Jackson 
>> wrote:
>>
>>> 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 <
>>> kiki...@gmail.com> wrote:
>>>
 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 we will handle it in a new one, with a repro case

 thanks


 On Thu, Mar 8, 2018 at 6:41 PM, Jamie Jackson 
 wrote:

> I'm having big problems with Vagrant lately:
>
>
>- My private network's IP gets properly assigned (to eth1) on the
>first vagrant up
>- On the first vagrant reload, the IP is inappropriately assigned
>to eth0 (the regular NAT network nic), and the IP now shows on both 
> eth0
>and eth1
>- On third vagrant reload, eth1 is disabled
>
>
> Upon the third vagrant reload, my project is trashed because I can't
> use the private network anymore. My project has a rather long initial
> vagrant up so it is very painful for my team to have to destroy 
> frequently.
>
> I see lots of networking issues reported on GitHub, so I don't have
> much hope that this one will get fixed anytime soon, so I'm looking for 
> any
> workarounds you might have.
>
> Here's a detail of my problem:
> https://github.com/hashicorp/vagrant/issues/9510#issuecomment-371560182
>
> Thanks,
> Jamie
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines
> - https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> 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 vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/CA%2BonWPf5SUJ_AM0LS2wQv__%2B5W29uzHV_%3Die%2BqKrW-0WeKGiuQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



 --
 Alvaro

 --
 This mailing list is governed under the HashiCorp Community Guidelines
 - https://www.hashicorp.com/community-guidelines.html. Behavior in
 violation of those guidelines may result in your removal from this mailing
 list.

 GitHub Issues: https://github.com/mitchellh/vagrant/issues
 IRC: #vagrant on Freenode
 ---
 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 vagrant-up+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/vagrant-up/CAHqq0eztCZRWJvSDdKGQ2QwjaBkhBYLKXhoMJ0G8mayJt7FPbA%40mail.gmail.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>> --
>> This mailing list is governed under the HashiCorp Community Guidelines -
>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>> violation of those guidelines may result in your removal from this mailing
>>

Re: [vagrant-up] Private IP Assigned to Wrong NIC

2018-03-13 Thread Alvaro Miranda Aguilera

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 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 Jackson 
> wrote:
>
>> I've copied the contents to https://github.com/hashicor
>> p/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 <
>> kiki...@gmail.com> wrote:
>>
>>> 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 we will handle it in a new one, with a repro case
>>>
>>> thanks
>>>
>>>
>>> On Thu, Mar 8, 2018 at 6:41 PM, Jamie Jackson 
>>> wrote:
>>>
 I'm having big problems with Vagrant lately:


- My private network's IP gets properly assigned (to eth1) on the
first vagrant up
- On the first vagrant reload, the IP is inappropriately assigned
to eth0 (the regular NAT network nic), and the IP now shows on both eth0
and eth1
- On third vagrant reload, eth1 is disabled


 Upon the third vagrant reload, my project is trashed because I can't
 use the private network anymore. My project has a rather long initial
 vagrant up so it is very painful for my team to have to destroy frequently.

 I see lots of networking issues reported on GitHub, so I don't have
 much hope that this one will get fixed anytime soon, so I'm looking for any
 workarounds you might have.

 Here's a detail of my problem: https://github.com/ha
 shicorp/vagrant/issues/9510#issuecomment-371560182

 Thanks,
 Jamie

 --
 This mailing list is governed under the HashiCorp Community Guidelines
 - https://www.hashicorp.com/community-guidelines.html. Behavior in
 violation of those guidelines may result in your removal from this mailing
 list.

 GitHub Issues: https://github.com/mitchellh/vagrant/issues
 IRC: #vagrant on Freenode
 ---
 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 vagrant-up+unsubscr...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/ms
 gid/vagrant-up/CA%2BonWPf5SUJ_AM0LS2wQv__%2B5W29uzHV_%3Die%2
 BqKrW-0WeKGiuQ%40mail.gmail.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> --
>>> Alvaro
>>>
>>> --
>>> This mailing list is governed under the HashiCorp Community Guidelines -
>>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>>> violation of those guidelines may result in your removal from this mailing
>>> list.
>>>
>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>>> IRC: #vagrant on Freenode
>>> ---
>>> 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 vagrant-up+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/vagrant-up/CAHqq0eztCZRWJvSDdKGQ2QwjaBkhBYLKXhoMJ0G8mayJ
>>> t7FPbA%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> 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 vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/CA%2BonWPd7KoG0Aj85n1My6SAoC98Se9
>

Re: [vagrant-up] Private IP Assigned to Wrong NIC

2018-03-12 Thread Jamie Jackson

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 Jackson  wrote:

> 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 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 we will handle it in a new one, with a repro case
>>
>> thanks
>>
>>
>> On Thu, Mar 8, 2018 at 6:41 PM, Jamie Jackson 
>> wrote:
>>
>>> I'm having big problems with Vagrant lately:
>>>
>>>
>>>- My private network's IP gets properly assigned (to eth1) on the
>>>first vagrant up
>>>- On the first vagrant reload, the IP is inappropriately assigned to
>>>eth0 (the regular NAT network nic), and the IP now shows on both eth0 and
>>>eth1
>>>- On third vagrant reload, eth1 is disabled
>>>
>>>
>>> Upon the third vagrant reload, my project is trashed because I can't use
>>> the private network anymore. My project has a rather long initial vagrant
>>> up so it is very painful for my team to have to destroy frequently.
>>>
>>> I see lots of networking issues reported on GitHub, so I don't have much
>>> hope that this one will get fixed anytime soon, so I'm looking for any
>>> workarounds you might have.
>>>
>>> Here's a detail of my problem: https://github.com/ha
>>> shicorp/vagrant/issues/9510#issuecomment-371560182
>>>
>>> Thanks,
>>> Jamie
>>>
>>> --
>>> This mailing list is governed under the HashiCorp Community Guidelines -
>>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>>> violation of those guidelines may result in your removal from this mailing
>>> list.
>>>
>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>>> IRC: #vagrant on Freenode
>>> ---
>>> 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 vagrant-up+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/vagrant-up/CA%2BonWPf5SUJ_AM0LS2wQv__%2B5W29uzHV_%3Die%2
>>> BqKrW-0WeKGiuQ%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Alvaro
>>
>> --
>> This mailing list is governed under the HashiCorp Community Guidelines -
>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>> violation of those guidelines may result in your removal from this mailing
>> list.
>>
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> ---
>> 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 vagrant-up+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/vagrant-up/CAHqq0eztCZRWJvSDdKGQ2QwjaBkhBYLKXhoMJ0G8mayJ
>> t7FPbA%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CA%2BonWPd7KoG0Aj85n1My6SAoC98Se94ZKJ4C5v7Uag9BM67tGw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Private IP Assigned to Wrong NIC

2018-03-08 Thread Jamie Jackson

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 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 we will handle it in a new one, with a repro case
>
> thanks
>
>
> On Thu, Mar 8, 2018 at 6:41 PM, Jamie Jackson 
> wrote:
>
>> I'm having big problems with Vagrant lately:
>>
>>
>>- My private network's IP gets properly assigned (to eth1) on the
>>first vagrant up
>>- On the first vagrant reload, the IP is inappropriately assigned to
>>eth0 (the regular NAT network nic), and the IP now shows on both eth0 and
>>eth1
>>- On third vagrant reload, eth1 is disabled
>>
>>
>> Upon the third vagrant reload, my project is trashed because I can't use
>> the private network anymore. My project has a rather long initial vagrant
>> up so it is very painful for my team to have to destroy frequently.
>>
>> I see lots of networking issues reported on GitHub, so I don't have much
>> hope that this one will get fixed anytime soon, so I'm looking for any
>> workarounds you might have.
>>
>> Here's a detail of my problem: https://github.com/ha
>> shicorp/vagrant/issues/9510#issuecomment-371560182
>>
>> Thanks,
>> Jamie
>>
>> --
>> This mailing list is governed under the HashiCorp Community Guidelines -
>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>> violation of those guidelines may result in your removal from this mailing
>> list.
>>
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> ---
>> 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 vagrant-up+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/vagrant-up/CA%2BonWPf5SUJ_AM0LS2wQv__%2B5W29uzHV_%3Die%
>> 2BqKrW-0WeKGiuQ%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Alvaro
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> 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 vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/CAHqq0eztCZRWJvSDdKGQ2QwjaBkhB
> YLKXhoMJ0G8mayJt7FPbA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CA%2BonWPcVivVVDZLgaBXUGMUJBvvMOXTDDBpEH8204KvthdbWhg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Private IP Assigned to Wrong NIC

2018-03-08 Thread Alvaro Miranda Aguilera

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 we will handle it in a new one, with a repro case

thanks


On Thu, Mar 8, 2018 at 6:41 PM, Jamie Jackson  wrote:

> I'm having big problems with Vagrant lately:
>
>
>- My private network's IP gets properly assigned (to eth1) on the
>first vagrant up
>- On the first vagrant reload, the IP is inappropriately assigned to
>eth0 (the regular NAT network nic), and the IP now shows on both eth0 and
>eth1
>- On third vagrant reload, eth1 is disabled
>
>
> Upon the third vagrant reload, my project is trashed because I can't use
> the private network anymore. My project has a rather long initial vagrant
> up so it is very painful for my team to have to destroy frequently.
>
> I see lots of networking issues reported on GitHub, so I don't have much
> hope that this one will get fixed anytime soon, so I'm looking for any
> workarounds you might have.
>
> Here's a detail of my problem: https://github.com/
> hashicorp/vagrant/issues/9510#issuecomment-371560182
>
> Thanks,
> Jamie
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> 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 vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/CA%2BonWPf5SUJ_AM0LS2wQv__%2B5W29uzHV_%3Die%2BqKrW-
> 0WeKGiuQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0eztCZRWJvSDdKGQ2QwjaBkhBYLKXhoMJ0G8mayJt7FPbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Private IP Assigned to Wrong NIC

Re: [vagrant-up] Private IP Assigned to Wrong NIC

Re: [vagrant-up] Private IP Assigned to Wrong NIC

Re: [vagrant-up] Private IP Assigned to Wrong NIC

Re: [vagrant-up] Private IP Assigned to Wrong NIC

5 matches

Site Navigation

Mail list logo

Footer information