Re: [vagrant-up] vagrant up error

2020-02-14 Thread Alvaro Miranda Aguilera 
hello

macos have a new security settings

make sure to go to settings security and accept virtualbox kernel drivers

alvaro

On Thu, Feb 13, 2020 at 5:21 AM Robert McDougal 
wrote:

> I am new to using vagrant, when I try to run the vagrant up command after
> doing the vagrant init, after following the tutorial directly from vagrants
> website, I keep getting the error saying "The virtual machine
> 'vagrant_1_default_1581565348939_70941' has terminated unexpectedly during
> startup with exit code 1 (0x1)". and when I try to start it through
> virtual box I get the error "VERR_VM_DRIVER_NOT_INSTALLED (-1908)" I cannot
> figure out what I am supposed to do to avoid this, I am using Mac OS X.
> Thank you
>
> --
> 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/755c59dd-ae4f-4582-bd24-b3252bb2013c%40googlegroups.com
> 
> .
>


-- 
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/CAHqq0exikqyU_8bNkFWLGnLPVBd_weKD62fxOS%2BU6WUj5sCq_Q%40mail.gmail.com.

Re: [vagrant-up] How-to specify a trigger to run before a specific provisioner script

2020-02-14 Thread Steve Freeman 
Okay, but how do I obtain the provisioner's name so I can conditionally 
execute the code?

On Tuesday, February 11, 2020 at 3:48:23 PM UTC-5, Brian Cain wrote:
>
>
>
> On Tue, Feb 11, 2020 at 12:29 PM Steve Freeman  > wrote:
>
>> I'm trying to write out a configuration file based on the state of 
>> execution at that point in the overall provisioning process.  If I don't 
>> use a trigger, then the code will execute the code to write the file with 
>> different parameters while the Vagrantfile is being evaluated. The 
>> resulting file is the last one generated. The file isn't just a handful of 
>> properties to be written or I'd pass the values as arguments and write the 
>> file locally in the provisioning script.
>>
>> Here is what I'd like to be able to do:
>>
>> config.trigger.before [:up,:provision], :provisioner_name => 
>> "install" do |trigger|
>> trigger.info = "Generate install configuration"
>> trigger.ruby do |env, machine|
>> puts "generating configuration for 
>> #{json['version'][0]}"
>> generate_configuration( json, baseOS, node_name )
>> end
>> end
>>
>
> You can write a trigger that runs before a given Vagrant hook, i.e. before 
> the provision step:
>
> https://www.vagrantup.com/docs/triggers/usage.html#hooks
>
> Please note the additional *type* option that defines this trigger as a 
> hook.
>
> config.trigger.before :provisioner_run, type: :hook do |t|
>   t.info = "Before the provision!"  t.ruby do |env,machine|
> puts "ruby stuff!"
> generate_stuff()
>   endend
>
>  
>
>>
>>
>> On Tuesday, February 11, 2020 at 3:21:53 PM UTC-5, Brian Cain wrote:
>>>
>>> Hey Steve - 
>>>
>>> On Tue, Feb 11, 2020 at 8:10 AM Steve Freeman  wrote:
>>>
 I have a shell provisioners specified with names, like so:

 config.vm.provision "disk", type: "shell", path: "provision.ps1"

 How do I get a trigger to execute specific code only before this 
 particular provisioner?

>>>
>>> What kind of trigger are you writing? If it's just a trigger that runs 
>>> on the guest, the easiest thing to do
>>> would be to use a regular provisioner instead.
>>>  
>>>
 -- 
 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 vagra...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/vagrant-up/416eb13e-c41c-40cc-97f2-cfadd64eb1f1%40googlegroups.com
  
 
 .

>>>
>>>
>>> -- 
>>> Brian Cain
>>>
>> -- 
>> 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 vagra...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/446d83dc-2dbf-4bc8-8fcc-0a5fc2f711ed%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Brian Cain
>

-- 
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/69a43bfd-54c5-4c1c-bb15-04fea1fc2edb%40googlegroups.com.

Re: [vagrant-up] How-to specify a trigger to run before a specific provisioner script

2020-02-14 Thread Brian Cain 
On Fri, Feb 14, 2020 at 10:53 AM Steve Freeman  wrote:

> Okay, but how do I obtain the provisioner's name so I can conditionally
> execute the code?
>

That would run before *all* provisioners. You can't run a trigger before a
specific provisioner at the moment.
You can run provisioners before or after other provisioners, but
unfortunately those only run on the guest, and aren't what you want based
on the method
you're using to generate configuration.


>
> On Tuesday, February 11, 2020 at 3:48:23 PM UTC-5, Brian Cain wrote:
>>
>>
>>
>> On Tue, Feb 11, 2020 at 12:29 PM Steve Freeman  wrote:
>>
>>> I'm trying to write out a configuration file based on the state of
>>> execution at that point in the overall provisioning process.  If I don't
>>> use a trigger, then the code will execute the code to write the file with
>>> different parameters while the Vagrantfile is being evaluated. The
>>> resulting file is the last one generated. The file isn't just a handful of
>>> properties to be written or I'd pass the values as arguments and write the
>>> file locally in the provisioning script.
>>>
>>> Here is what I'd like to be able to do:
>>>
>>> config.trigger.before [:up,:provision], :provisioner_name =>
>>> "install" do |trigger|
>>> trigger.info = "Generate install configuration"
>>> trigger.ruby do |env, machine|
>>> puts "generating configuration for
>>> #{json['version'][0]}"
>>> generate_configuration( json, baseOS, node_name )
>>> end
>>> end
>>>
>>
>> You can write a trigger that runs before a given Vagrant hook, i.e.
>> before the provision step:
>>
>> https://www.vagrantup.com/docs/triggers/usage.html#hooks
>>
>> Please note the additional *type* option that defines this trigger as a
>> hook.
>>
>> config.trigger.before :provisioner_run, type: :hook do |t|
>>   t.info = "Before the provision!"  t.ruby do |env,machine|
>> puts "ruby stuff!"
>> generate_stuff()
>>   endend
>>
>>
>>
>>>
>>>
>>> On Tuesday, February 11, 2020 at 3:21:53 PM UTC-5, Brian Cain wrote:

 Hey Steve -

 On Tue, Feb 11, 2020 at 8:10 AM Steve Freeman 
 wrote:

> I have a shell provisioners specified with names, like so:
>
> config.vm.provision "disk", type: "shell", path: "provision.ps1"
>
> How do I get a trigger to execute specific code only before this
> particular provisioner?
>

 What kind of trigger are you writing? If it's just a trigger that runs
 on the guest, the easiest thing to do
 would be to use a regular provisioner instead.


> --
> 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 vagra...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/416eb13e-c41c-40cc-97f2-cfadd64eb1f1%40googlegroups.com
> 
> .
>


 --
 Brian Cain

>>> --
>>> 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 vagra...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/vagrant-up/446d83dc-2dbf-4bc8-8fcc-0a5fc2f711ed%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>> Brian Cain
>>
> --
> 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] How to show real ip client in flask on vagrant VM

2020-02-14 Thread Javad Rajabzade 
hi guys

i'm a python web developer
i have problem to return real ip client on remote

https://stackoverflow.com/questions/60133862/how-to-show-real-ip-client-in-flask-on-vagrant-vm/60236440#60236440

i tray for fix this problem but don't done :(
i have problem with ip 10.0.2.2

-- 
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/b1aa0e03-00d6-44b9-9b5b-73f39714714e%40googlegroups.com.