Re: [vagrant-up] Showing Some error in Ruby

[Alvaro Miranda Aguilera]

Hello

Does this happen with a vagrant file?

can you try on a new directory?

vagrant init -m hashicorp/bionic64
vagrant status

?

does this give error?

if no, then could be some error on your Vagrantfile

please share it here


On Mon, Sep 18, 2023 at 9:54 PM Aashish Jha  wrote:

> I m having this error as I installed 5 Vms... after that when every I want
> to see the status of the vagrant. It shows me this error.
>
> /Users/aashishjha/.vagrant.d/gems/3.1.4/gems/rubyhacks-0.1.5/lib/rubyhacks.rb:342:in
> `-@': can't modify frozen String: "=" (FrozenError)
> from /opt/vagrant/embedded/lib/ruby/3.1.0/rubygems/requirement.rb:114:in
> `parse'
> from /opt/vagrant/embedded/lib/ruby/3.1.0/rubygems/requirement.rb:138:in
> `block in initialize'
> from /opt/vagrant/embedded/lib/ruby/3.1.0/rubygems/requirement.rb:138:in
> `map!'
> from /opt/vagrant/embedded/lib/ruby/3.1.0/rubygems/requirement.rb:138:in
> `initialize'
> from
> /opt/vagrant/embedded/gems/gems/vagrant-2.3.7/lib/vagrant/box_collection.rb:280:in
> `new'
> from
> /opt/vagrant/embedded/gems/gems/vagrant-2.3.7/lib/vagrant/box_collection.rb:280:in
> `block in find'
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/9113120c-3421-4583-aa7d-86f75fec1fb3n%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ez2KvN1u_c1%3DLKOepXQo%2B1X9m_S1Y1QHOQoA1L4_z2XPQ%40mail.gmail.com.

Re: [vagrant-up] Change working directory for the shell provisioner

[Alvaro Miranda Aguilera]

Hello

You can try to change the format of the script

to be inside a block

$script = <<-SCRIPT

cd /home/vagrant/pep_code
git init
git config --global user.name \"Giacomo\"
git config --global user.email \"[redacted]\"
git add * && git commit -m \"fix\"
mkdir build && cd build
CC=clang CXX=clang++ cmake -DWITH_CASTOR=OFF ..
ninja

SCRIPT

Vagrant.configure("2") do |config|
  config.vm.provision "shell", inline: $script
end





On Thu, Jun 29, 2023 at 6:46 PM Giacomo Tommaso Petrucci <
giacomo.tom.petru...@gmail.com> wrote:

> Thank you for your answers. Yes, this is a little inconvenient but doable.
>
> Regards,
>
> Giacomo Tommaso Petrucci
>
> Il giorno giovedì 29 giugno 2023 alle 17:52:28 UTC+2 dnmo...@gmail.com ha
> scritto:
>
>> If neither one is an option you have to put multiple commands together
>> like cd /home/path1/subpath && ninja
>>
>> On Thursday, June 29, 2023 at 11:50:05 AM UTC-4 dnmo...@gmail.com wrote:
>>
>>> Jim is correct.
>>>
>>> You typically would want to run the command from the root with the full
>>> path e.g. ./home/vagrant/pep_code/build/ninja (if ninja is a script).
>>>
>>> If ninja is an app, you would do something like ninja >> file> e.g. ninja  /home/vagrant/pep_code/build/
>>>
>>> On Thursday, June 29, 2023 at 11:06:20 AM UTC-4 Jim McGinness wrote:
>>>
 Each shell provisioning line runs as its own process. Directory changes
 do not persist from one line to the next. You will need to gather your
 individual lines into an actual script to get the result you want. For more
 info, see

 https://developer.hashicorp.com/vagrant/docs/provisioning/shell

  -- jmcg

 On Thu, Jun 29, 2023 at 9:51 AM Giacomo Tommaso Petrucci <
 giacomo.to...@gmail.com> wrote:

> Greetings,
>
> I wrote the following Vagrantfile:
>
> Vagrant.configure("2") do |config|
>   config.vm.box = "ubuntu/jammy64"
>   config.vm.synced_folder "pep_code", "/home/vagrant/pep_code"
>
>   # Update and install dependencies
>   config.vm.provision "shell", inline: "echo Updating..."
>   config.vm.provision "shell", inline: "sudo apt-get update && sudo
> apt-get -y upgrade"
>   config.vm.provision "shell", inline: "sudo apt-get -y install  clang
> ninja-build golang golang-goprotobuf-dev ccache distcc git cmake valgrind
> libboost-all-dev zlib1g-dev libbz2-dev libsqlite3-dev libcurl4-openssl-dev
> curl libpam0g-dev libssl-dev libreadline-dev patch vim flex qtbase5-dev
> qtdeclarative5-dev qttools5-dev qttools5-dev-tools libunwind-dev libc6-dev
> libc6-dev-i386 software-properties-common gcc-multilib"
>   config.vm.provision "file", source: "pep_code", destination:
> "/home/vagrant/pep_code"
>   config.vm.provision "shell", inline: "cd /home/vagrant/pep_code"
>   config.vm.provision "shell", inline: "git init"
>   config.vm.provision "shell", inline: "git config --global user.name
> \"Giacomo\""
>   config.vm.provision "shell", inline: "git config --global user.email
> \"[redacted]\""
>   config.vm.provision "shell", inline: "git add * && git commit -m
> \"fix\""
>   config.vm.provision "shell", inline: "mkdir build && cd build"
>   config.vm.provision "shell", inline: "CC=clang CXX=clang++ cmake
> -DWITH_CASTOR=OFF .."
>   config.vm.provision "shell", inline: "ninja"
> end
>
> It fails while provisioning with the following message:
>
> default: CMake Error: The source directory "/home" does not appear to
> contain CMakeLists.txt.
>default: Specify --help for usage, or press the help button on the
> CMake GUI.
> The SSH command responded with a non-zero exit status. Vagrant
> assumes that this means the command failed. The output for this command
> should be in the log above. Please read the output to determine what
> went wrong.
>
>
> I was expecting the lines
>
> config.vm.provision "shell", inline: "cd /home/vagrant/pep_code"
>
> and
>
> config.vm.provision "shell", inline: "mkdir build && cd build"
>
> to change the working directory of the provisioning process, but this
> doesn't seem the case. Docker has an instruction for this, WORKDIR. Does
> Vagrant have something similar? A quick Google search didn't turn up
> anything.
> Thank you for your help,
>
> Giacomo Tommaso Petrucci
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> You received this message because you are subscribed to the Google
> Groups "Vagrant" group.
> To unsubscribe from this group and stop 

Re: [vagrant-up] Re: Vagrant plugin issues

[Alvaro Miranda Aguilera]

Hello

The error message is complaining about plugin

so you need to make sure the shell part is a valid script

it seem the formatting is wrong around this line



  sudo apt-get install docker-ce docker-ce-cli containerd.io
docker-buildx-plugin
docker-compose-  plugin -y

i think should be

  sudo apt-get install docker-ce docker-ce-cli containerd.io
docker-buildx-plugin
docker-compose-plugin -y

Better will be make sure you are using a good / valid Vagrantfile, go and
check as possible a copy of the file from where you got this

if this is from a book, try to get the commands they want you to run

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0exKJrinDjKXm4dVZ%3DddVtbQuGwii-a_vh6fBKyN3tVabg%40mail.gmail.com.

Re: [vagrant-up] facing challenges while commanding yum install httpd in my centos

[Alvaro Miranda Aguilera]

error message is

- your network is resolving that url mirrorlist.centos.org to an IPV6
- your machine can't connect to that Ip over IPV6

so i would suggest disable IPV6 on yum or the OS

you can check the documentation for the OS vendor

ie
https://support.cpanel.net/hc/en-us/articles/7021847859095-How-to-force-YUM-DNF-to-use-IPv4


On Mon, Jun 19, 2023 at 9:17 PM Rishabh Anand 
wrote:

>
> Loaded plugins: fastestmirror
> Determining fastest mirrors
> Could not retrieve mirrorlist
> http://mirrorlist.centos.org/?release=7=x86_64=os=vag
> error was
> 14: curl#7 - "Failed to connect to 2600:1f16:c1:5e01:4180:6610:5482:c1c0:
> Network is unreachable"
>
>
>  One of the configured repositories failed (Unknown),
>  and yum doesn't have enough cached data to continue. At this point the
> only
>  safe thing yum can do is fail. There are a few ways to work "fix" this:
>
>  1. Contact the upstream for the repository and get them to fix the
> problem.
>
>  2. Reconfigure the baseurl/etc. for the repository, to point to a
> working
> upstream. This is most often useful if you are using a newer
> distribution release than is supported by the repository (and the
> packages for the previous distribution release still work).
>
>  3. Run the command with the repository temporarily disabled
> yum --disablerepo= ...
>
>  4. Disable the repository permanently, so yum won't use it by
> default. Yum
> will then just ignore the repository until you permanently enable
> it
> again or use --enablerepo for temporary usage:
>
> yum-config-manager --disable 
> or
> subscription-manager repos --disable=
>
>  5. Configure the failing repository to be skipped, if it is
> unavailable.
> Note that yum will try to contact the repo. when it runs most
> commands,
> so will have to try and fail each time (and thus. yum will be be
> much
> slower). If it is a very temporary problem though, this is often a
> nice
> compromise:
>
> yum-config-manager --save
> --setopt=.skip_if_unavailable=true
>
> Cannot find a valid baseurl for repo: base/7/x86_64
>
>
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/d37113a9-9407-49a3-852e-930710db06den%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0exbB0%3DynWx5Tc8sLOUgJNfwh%3DK-5JwA2Zq7vfZLevvHAA%40mail.gmail.com.

Re: [vagrant-up] vagrant 2.3.4, vbox 7, ubuntu 22 : Do they work together?

[Alvaro Miranda Aguilera]

hello

what happens if you restart the vm from virtualbox ui ?

can you share screenshot what you see?

On Sat, May 20, 2023 at 5:59 PM jay vyas 
wrote:

> Hi folks.  I was trying some relatively unopinionated vagrant files with
> ubuntu and private networks.   It appears that my VM gets stuck in the
> "gurumeditation" state, though.
>
> Has an anyone tried making a Vagrant virtual box instance on ubuntu 22?
> If so, does it work for you with private IPs ?
>
> - VBoxManage -v
>
> *7.0.8r156879*- vagrant version
> [Vagrantfile] Loading default settings from settings.yaml
>
> *Installed Version: 2.3.4Latest Version: 2.3.6*
>
> *PS *
>
> ( also posted this message here
> https://discuss.hashicorp.com/t/vagrant-up-ubuntu-22-gurumeditation-state/54018)
> but I feel like the google group for vagrant is probably a better place to
> ask it, since the hashicorp message board is likely mostly Terraform stuff)
>
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/10587318-70f6-4c5a-882f-3593590f4d4cn%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ex9pquFCrW2LD%3DSP3%3D7pHYPrsuaf_tmxxoDx6MeaKUGNg%40mail.gmail.com.

Re: [vagrant-up] mkdir error

[Alvaro Miranda Aguilera]

hello

option 1
mkdir opt/
mkdir opt/devopsdir


option 2
mkdir -p opt/devopsdir

but if this is on OS /opt then command is missing leading slash

mkdir /opt/devopsdir

On Mon, May 22, 2023 at 4:37 PM Ekwonye Chibuzor Michael <
mcdennisekwo...@gmail.com> wrote:

> I tried creating directories and i got this error below
>
> mkdir: cannot create directory ‘opt/devopsdir/’: No such file or directory
>
> How do i correct this error fam.
>
>
> Regards.
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/4832384a-cfcd-4adf-b383-8acb0e09537dn%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ewL1T%3Dt00hyKqkamxSbHZodoE%2Bf1SqoFoXKkBNGZECUSQ%40mail.gmail.com.

Re: [vagrant-up] unable to download packages in vagrant(VM Virtualbox)

[Alvaro Miranda Aguilera]

Hello

Boxes with the form of "name" are local boxes that should have either a
remote url, or can be added with vagrant box add .. command

If you go to vagrant cloud and find the image you want to use
you can update the Vagrantfile to the form of repo/box and vagrant will
download the box for you


ie ubuntu
https://app.vagrantup.com/ubuntu

box ubuntu/jammy64
https://app.vagrantup.com/ubuntu/boxes/jammy64






On Wed, May 17, 2023 at 8:20 AM KailaAbraham Paul <
kailaabrahamp...@gmail.com> wrote:

> Failed to download metadata for repo 'appstream': Cannot prepare internal
> mirrorlist: No URLs in mirrorlist
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/a82d3909-b492-4f9c-a472-b649c3c15ce5n%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0exrx4zHRo%2BxGSD1EAwkLqk1gS6K8Py92qon0xngoP1tZA%40mail.gmail.com.

Re: [vagrant-up] supHardenedWinVerifyProcess failed with -5607: ntdll.dll on Windows 11 Pro Insider

[Alvaro Miranda Aguilera]

Error is from virtualbox.

Try to open the GUI for Virtualbox, find the VM, and try to stop / start
manually.

After installing virtualbox, is good to test it works, create and boot a VM.



On Thu, May 11, 2023 at 4:35 PM Amitabh Suman 
wrote:

> I am trying to issue vagrant up command for geerlingguy/centos7 on my Windows
> 11 Pro Insider OS
>
> Versions : (Vagrant 2.3.4, Oracle VirtaulBox Version 7.0.8 r156879
> (Qt5.15.2)).
> OS settings : Firewall disabled, Antivirus disabled
> RAM assigned to VMs : 2GB
>
> No matter what I do, "vagrant up" fails always with the below error. I am
> unable to find any help on this, not even ChatGPT could help. Can anyone of
> you kind helpful folks, help me out.
>
> 3078.3554:   7ffa4da8b000-7ffa4da8dfff 0x0008/0x0080 0x100
> \Device\HarddiskVolume3\Windows\System32\ntdll.dll
> 3078.3554:   7ffa4da8e000-7ffa4da8efff 0x0004/0x0080 0x100
> \Device\HarddiskVolume3\Windows\System32\ntdll.dll
> 3078.3554:   7ffa4da8f000-7ffa4db07fff 0x0002/0x0080 0x100
> \Device\HarddiskVolume3\Windows\System32\ntdll.dll
> 3078.3554:   7ffa4db08000-7ffa4db09fff 0x/0x0080 0x100
> \Device\HarddiskVolume3\Windows\System32\ntdll.dll
> 3078.3554:   7ffa4db0a000-7ffe 0x0001/0x 0x000
> 3078.3554: VBoxHeadless.exe: Differences in section #8 (.rsrc) between
> file and memory:
> 3078.3554:   7ff7d09525f8 / 0x01125f8: 00 != 50
> 3078.3554:   7ff7d09525f9 / 0x01125f9: 00 != 41
> 3078.3554:   7ff7d09525fa / 0x01125fa: 00 != 44
> 3078.3554:   7ff7d09525fb / 0x01125fb: 00 != 44
> 3078.3554:   7ff7d09525fc / 0x01125fc: 00 != 49
> 3078.3554:   7ff7d09525fd / 0x01125fd: 00 != 4e
> 3078.3554:   7ff7d09525fe / 0x01125fe: 00 != 47
> 3078.3554:   7ff7d09525ff / 0x01125ff: 00 != 58
> 3078.3554:   Restored 0xa08 bytes of original file content at
> 7ff7d09525f8
> 3078.3554: Error (rc=-5607):
> 3078.3554: ntdll.dll: SizeOfImage (0x218000) isn't close enough to the
> mapping size (0x21a000)
> 3078.3554: Error (rc=-5607):
> 3078.3554: supHardenedWinVerifyProcess failed with -5607: ntdll.dll:
> SizeOfImage (0x218000) isn't close enough to the mapping size (0x21a000)
> 3078.3554: Error -5607 in supR3HardNtChildPurify! (enmWhat=5)
> 3078.3554: supHardenedWinVerifyProcess failed with -5607: ntdll.dll:
> SizeOfImage (0x218000) isn't close enough to the mapping size (0x21a000)
>
> What possibly am I doing wrong or what settings needs to be done to fix
> it. I have attached the hardening logs as well. Kindly help me.
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/e6c9c648-27d1-4353-ab44-33259fa71a86n%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0eyAqqJMCFJYQunTAtkrzqo3UZjydc4MdQoXvB2Z3b6_xQ%40mail.gmail.com.

Re: [vagrant-up] How to add a new platform for Vagrant?

[Alvaro Miranda Aguilera]

hello

check list of plugins to confirm there is not one already

https://github.com/hashicorp/vagrant/wiki/Available-Vagrant-Plugins

documentation to build provider is here
https://developer.hashicorp.com/vagrant/docs/plugins/providers


On Sun, Sep 11, 2022 at 8:29 AM 'hack...@yahoo.com' via Vagrant <
vagrant-up@googlegroups.com> wrote:

> Hello,
> Currently, Vagrant is available for VirtualBox, KVM, Hyper-V, Docker
> containers, VMware, and AWS. How can I add new platform for it?
>
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/d2b89d5c-9a88-4dff-bffb-02a80706be51n%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0eyHCrrpVXOtDE42dhNdZHX84vXhUUQ1Jg6aDGp5UUM42g%40mail.gmail.com.

Re: [vagrant-up] How to build a newer version of linux kernel in Virtualbox?

[Alvaro Miranda Aguilera]

Hello

You can upgre kernel, then need to reboot, then build virtual guest
additions, then vagrant reload should work fine

however you should be able to create an updated vagrant box with packer and
vagrant builder

https://developer.hashicorp.com/packer/plugins/builders/vagrant#example

this will generate a ready to use box.


On Tue, Oct 4, 2022 at 5:45 AM Ruihua Chan  wrote:

> Hi all,
>
> I want to use the newest version of linux kernel: linux v6.0-rc7 in
> Virtualbox.
> So I plan to download a Ubuntu22.04 box from VagrantCloud and install the
> newer linux kernel in it.Is it possible to realize?
>
> Any advice will help.Thanks in advance.
>
> > Chan
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/12b0909c-0516-4332-85bc-93028c162df7n%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0exyH_AHBh_ekFm4REN8%3DDOuUienP02vhrd8RA0hbOhUdw%40mail.gmail.com.

Re: [vagrant-up] How do I fix this issues

[Alvaro Miranda Aguilera]

Hello

make sure you are in a directory where your use have permissions to create
files

in that way when you run vagrant init, it will create the Vagranfile file
without problems

Thanks
Alvaro


On Tue, Mar 29, 2022 at 10:21 AM Vic 
wrote:

> The user that is running Vagrant doesn't have the proper permissions
> to write a Vagrantfile to the specified location. Please ensure that
> you call `vagrant init` in a location where the proper permissions
> are in place to create a Vagrantfile.
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/5162811f-7560-430d-96f7-3561d181de5an%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ewYJ2RZSjhdMw-mXsDhrsim-0U4M8MMcCewCoTtLgQOsg%40mail.gmail.com.

Re: [vagrant-up] VAGRANT VSPHERE

[Alvaro Miranda Aguilera]

Vagrant had a community plugin, but if you are open to test, terraform have
native support for vsphere.

Vagrant community plugin, havent used in a long time, but used to work just
fine:
https://github.com/nsidc/vagrant-vsphere

terraform:
https://registry.terraform.io/providers/hashicorp/vsphere/latest/docs/resources/virtual_machine


On Wed, Jan 5, 2022 at 7:26 AM ROOKIE IT 
wrote:

> Does anyone know of documentation, book, or video of someone actually
> configuring VSPHERE utilizing vagrant to configure multiple Windows
> 2016/2019 servers? Or anything similar? I'm interested in this and would
> love somewhere to start. Thanks in advance.
>
> RIT
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/8eb70a27-44c0-4f20-a50c-69cb30da919dn%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ezgTUTcE0r5-bJAZvZvMFO8HFkKN8Rdt%3DcByqN_nQtOUw%40mail.gmail.com.

Re: [vagrant-up] Vagrand VMware

[Alvaro Miranda Aguilera]

hello

try

vagrant plugin list

if you see any plugin there, you can remove with

vagrant plugin uninstall 



On Wed, Jun 16, 2021 at 3:50 PM Леха СПАМ  wrote:

> Hello everyone. Installed Vagrand. I wanted to put it on ESXi but failed.
> I decided to reinstall on VirtualBox, but now I get the error "Vagrant
> encountered an unexpected communications error with the Vagrant VMware
> Utility driver. Please try to run the command again. If this error
> persists, please contact supp...@hashicorp.com " I deleted the utility a
> long time ago. Tell me how to fix it?
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/6c6afebc-2acc-4a13-9257-867d5dd7a792n%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0eyJZKCxBzhtnzqcVAV51fkMP7r9cL6_pLgL8gTaod3-bw%40mail.gmail.com.

Re: [vagrant-up] Vagrant syntax to remove just one box-version

[Alvaro Miranda Aguilera]

Hello

If you are comfortable with command line, you can remove the directory
version of the box you want to remove.

.vagrant.d/boxes/generic-VAGRANTSLASH-openbsd6/1.8.40/


On Fri, May 28, 2021 at 6:23 PM James E Keenan  wrote:

> I have a server on which I use Vagrant to install and manage VirtualBox
> VMs for various operating systems.  Over time I have installed 3
> different OpenBSD VMs.  The box for each of these was originally
> obtained from the listings at vagrantup.com.  Each box holds a different
> OpenBSD version.
>
> I believe the following command accurately lists the Vagrant box versions:
>
> ###
> $ ls -l .vagrant.d/boxes/generic-VAGRANTSLASH-openbsd6/
> total 2
> drwxr-xr-x  3 vmuser  vmuser   3 Nov  4  2018 1.8.40
> drwxr-xr-x  3 vmuser  vmuser   3 Oct  7  2019 1.9.34
> drwxr-xr-x  3 vmuser  vmuser   3 Feb  1  2020 2.0.6
> ###
>
> This data correlates with the output of this command:
>
> ###
> $ vagrant box list | grep -i openbsd
> generic/openbsd6  (virtualbox, 1.8.40)
> generic/openbsd6  (virtualbox, 1.9.34)
> generic/openbsd6  (virtualbox, 2.0.6)
> ###
>
> Problem:  I want to make sure that I am using the correct syntax to
> remove *one* of the boxes but not the others.  Suppose that I want to
> remove 1.8.40.  Is the following the correct way to remove that one and
> leave the other two untouched?
>
> ###
> vagrant box remove generic-openbsd6 --provider virtualbox --box-version
> 1.8.40
> ###
>
> Thank you very much.
> Jim Keenan
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/45adf0de-0631-50e3-6c5c-ff7141e45db2%40pobox.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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0eyQM2EmdLeRF1OT2WLHNrbWZqq%3DmyRZbYbhabFVQEPH-w%40mail.gmail.com.

Re: [vagrant-up] Not able to ping from one Host Virtual machine to different host Virtual machine in Vagrant

[Alvaro Miranda Aguilera]

from the 2 machines in different host that can' t ping each other

can you share

in the old days should have been

ifconfig -a
route print

in the new commands, i think is like

ip route
ip address



On Mon, May 17, 2021 at 10:41 AM Raghu H  wrote:

> No.. It's connected over the coprate LAN network
>
> On Mon, 17 May, 2021, 2:08 PM Alvaro Miranda Aguilera, 
> wrote:
>
>> are you using wifi on any of those host ?
>>
>>
>>
>> On Thu, May 13, 2021 at 9:14 PM Raghu H  wrote:
>>
>>> I am not able to ping between two virtual machines on different Host,
>>> But can ping between two virtual machines if they are in the same Host
>>> machine, using a Bridge network to communicate between the two different
>>> VM’s.
>>>
>>> Vagrantfile look like this on both VM,
>>> ENV['VAGRANT_NO_PARALLEL'] = 'yes' Vagrant.configure(2) do |config|
>>> config.vm.provision "shell", path: "bootstrap.sh" MasterCount = 1
>>> (1..MasterCount).each do |i| config.vm.define "kmaster2" do
>>> |masternode| masternode.vm.network "forwarded_port", guest: "80", host:
>>> "5050", auto_correct: "true" masternode.vm.box = "bento/ubuntu-20.04"
>>> masternode.vm.hostname = "kmaster2.example.com" masternode.vm.network
>>> "public_network", ip: "172.16.16.50", bridge: "ens160"
>>> masternode.vm.provider "virtualbox" do |v| v.name = "kmaster2" v.memory
>>> = 2048 v.cpus = 2 end end end
>>>
>>> please refer to the text diagrams below Ping between the Physical
>>> machine (241) and Physical machine (242) works ping between VM-11 and VM-12
>>> within the same physical machine works. Ping from VM-21 in Physical machine
>>> (242) to Physical machine (241) works But ping between VM-11 and VM-21 does
>>> not work. Also, ping from Physical machine 241 to VM-21 (in Phy machine
>>> 242) does not work
>>>
>>> Any leads would help.
>>>
>>> Physical machine (241)
>>>  | --- | | |VM-11 | | | --- | | | | 
>>> ---
>>> | | |VM-12 | | | --- | |--|
>>>
>>> Physical machine (242)
>>>  | --- | | |VM-21 | | | --- | | | | 
>>> ---
>>> | | |VM-22 | | | --- | |--|
>>>
>>> --
>>> 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/hashicorp/vagrant/issues
>>> Discuss: https://discuss.hashicorp.com/c/vagrant/24
>>> ---
>>> 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/36a404c2-b788-41ba-adbe-24c811470e5cn%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/36a404c2-b788-41ba-adbe-24c811470e5cn%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> 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/hashicorp/vagrant/issues
>> Discuss: https://discuss.hashicorp.com/c/vagrant/24
>> ---
>> 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/CAHqq0ezGDJBsVK4Q7vdDqihTTgkJSA4mPKmAw1GZTY48ZLe16w%40mail.gmail.com
>> <https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezGDJBsVK4Q7vdDqihTTgkJSA4mPKmAw1GZTY48ZLe16w%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavi

Re: [vagrant-up] Not able to ping from one Host Virtual machine to different host Virtual machine in Vagrant

[Alvaro Miranda Aguilera]

are you using wifi on any of those host ?



On Thu, May 13, 2021 at 9:14 PM Raghu H  wrote:

> I am not able to ping between two virtual machines on different Host, But
> can ping between two virtual machines if they are in the same Host machine,
> using a Bridge network to communicate between the two different VM’s.
>
> Vagrantfile look like this on both VM,
> ENV['VAGRANT_NO_PARALLEL'] = 'yes' Vagrant.configure(2) do |config|
> config.vm.provision "shell", path: "bootstrap.sh" MasterCount = 1
> (1..MasterCount).each do |i| config.vm.define "kmaster2" do |masternode|
> masternode.vm.network "forwarded_port", guest: "80", host: "5050",
> auto_correct: "true" masternode.vm.box = "bento/ubuntu-20.04"
> masternode.vm.hostname = "kmaster2.example.com" masternode.vm.network
> "public_network", ip: "172.16.16.50", bridge: "ens160"
> masternode.vm.provider "virtualbox" do |v| v.name = "kmaster2" v.memory =
> 2048 v.cpus = 2 end end end
>
> please refer to the text diagrams below Ping between the Physical machine
> (241) and Physical machine (242) works ping between VM-11 and VM-12 within
> the same physical machine works. Ping from VM-21 in Physical machine (242)
> to Physical machine (241) works But ping between VM-11 and VM-21 does not
> work. Also, ping from Physical machine 241 to VM-21 (in Phy machine 242)
> does not work
>
> Any leads would help.
>
> Physical machine (241)
>  | --- | | |VM-11 | | | --- | | | | 
> ---
> | | |VM-12 | | | --- | |--|
>
> Physical machine (242)
>  | --- | | |VM-21 | | | --- | | | | 
> ---
> | | |VM-22 | | | --- | |--|
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/36a404c2-b788-41ba-adbe-24c811470e5cn%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ezGDJBsVK4Q7vdDqihTTgkJSA4mPKmAw1GZTY48ZLe16w%40mail.gmail.com.

Re: [vagrant-up] Crostini / libvirt and crosvm

[Alvaro Miranda Aguilera]

hello
i dont have a chromebook with crostini, so i cant test

but wondering

how do you create containers manually? with lxc commands?

have you tried with vagrant lxc plugin?


On Thu, Apr 29, 2021 at 8:22 PM 'Andy Burnside' via Vagrant <
vagrant-up@googlegroups.com> wrote:

> Anyone know of a good way to manage Crostini on ChromeOS??
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/e1c05bb8-8deb-4dad-9ed3-14ce71d82d34n%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ewogUFgL%3DE3f3LMEszdtNY49uwNHmVrRO5wr7TO888oYw%40mail.gmail.com.

Re: [vagrant-up] Ansible's paths crossed in Vagrant Provision?

[Alvaro Miranda Aguilera]

hello

ansible requires to be setup to make it work

you could check pyenv and setup ansible as a virtual environment

however i would suggest consider using ansible-local that will run
directly  on the vm

https://www.vagrantup.com/docs/provisioning/ansible_local


On Mon, Mar 29, 2021 at 7:08 PM Kristina Bressler <
kristina.bress...@1905newmedia.com> wrote:

> Hi,
> When I started up a project with "vagrant up", everything was fine. But
> when I typed in "vagrant provision", I encountered this error:
> `System info:
>   Ansible 2.7.1; Vagrant 2.2.14; Darwin
>   Trellis 1.0.3: April 30th, 2019
> ---
> MODULE FAILURE
> See stdout/stderr for the exact error
> Traceback (most recent call last):
>   File "", line 113, in 
>   File "", line 105, in _ansiballz_main
>   File "", line 48, in invoke_module
>   File "/usr/lib/python3.6/imp.py", line 235, in load_module
> return load_source(name, filename, file)
>   File "/usr/lib/python3.6/imp.py", line 170, in load_source
> module = _exec(spec, sys.modules[name])
>   File "", line 618, in _exec
>   File "", line 678, in exec_module
>   File "", line 219, in
> _call_with_frames_removed
>   File "/tmp/ansible_setup_payload_1p7_kmoy/__main__.py", line 127, in
> 
> ImportError: attempted relative import with no known parent package
>
> An exception occurred during task execution. To see the full traceback,
> use -vvv. The error was: ImportError: attempted relative import with no
> known parent package
> fatal: [default]: FAILED! => {"changed": false, "module_stdout": "", "rc":
> 1}
> to retry, use: --limit @/Users/kiki/Code/project/trellis/dev.retry
>
> PLAY RECAP
> *
> default: ok=2changed=0unreachable=0failed=1
>
> /Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/multiprocessing/resource_tracker.py:216:
> UserWarning: resource_tracker: There appear to be 78 leaked semaphore
> objects to clean up at shutdown
>   warnings.warn('resource_tracker: There appear to be %d '
> Ansible failed to complete successfully. Any error output should be
> visible above. Please fix these errors and try again.`
>
> I looked in my folders at /usr/lib/ and I don't see *python3* folder in
> this location. I can only find *python2.7* folder. I even ran brew
> install python to install the latest version and I can see that it's
> downloading to /usr/local/lib/ where I can see two
> folders, python2.7 and python3.9.
>
> So the conclusion I got was that Ansible was trying to find python3 in
> wrong folder? So I think I have 2 options:
>
>1. try to brew install python in /usr/lib
>2. try to fix the Ansible's path to point to or find in usr/local/lib
>3. or copy the python3 folder from /usr/local/lib to /usr/lib
>
> So how do I do either one of the options or which is the best/alternative
> option?
>
> Do I type in the command line "ansible_python_interpreter = usr/local/lib"?
>
> My ansible version is 2.7.1.
>
> My pip3 version is pip 21.0.1 from
> /Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/pip
> (python 3.9)
>
> -Kristina
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/e661bdd3-1cfb-4a5a-aa5a-cfc7abdd8a55n%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ez3j6C3J%3D21iGFjUdnk7GUKe5x4TKiTYnQEfhJBF_YB-A%40mail.gmail.com.

Re: [vagrant-up] Multi-machine definition not honoured in embedded Vagrantfile

[Alvaro Miranda Aguilera]

t's in the embedded
> Vagrantfile.
> Currently, I am letting the users of this box copy the embedded
> Vagrantfile over the 'user vagrant file', after which it does get executed,
> and creates 3 nodes (the default value of replication_factor).
> However, it would be great if I can do the heavy lifting like above in the
> embedded Vagrantfile, so the user is not bothered by all these details, and
> can just init a simple Vagrantfile and start it.
>
> So the question is how to make constructions like above actually be
> executed in the embedded Vagrantfile?
>
> Thank you,
>
> Frits
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/9762DE44-6052-4A9F-82D0-7DAFF5FD203D%40gmail.com
> <https://groups.google.com/d/msgid/vagrant-up/9762DE44-6052-4A9F-82D0-7DAFF5FD203D%40gmail.com?utm_medium=email_source=footer>
> .
>
> Op 27 mrt. 2021, om 18:44 heeft Alvaro Miranda Aguilera 
> het volgende geschreven:
>
> Hello
>
> Can you share a zip file with code and instructions ?
>
> Thanks
> Alvaro
>
> On Wed, Mar 24, 2021 at 12:03 PM Frits Hoogland 
> wrote:
>
>> I am trying to create a vagrant box that launches a cluster of 3 VMs. The
>> Vagrantfile to accomplish this works when this definition is in the
>> Vagrantfile in the CWD. However, when I move this multi-machine definition
>> to the embedded Vagrantfile, vagrant ignores it and creates a default VM,
>> ignoring the named machine definitions.
>>
>> I read the documentation, which doesn’t say anything concrete about this,
>> only that multiple Vagrantfiles are merged before starting a vagrant box,
>> and that some definitions in the Vagrantfile are added, and some do
>> overwrite, which is not very descriptive.
>>
>> My first question is if this is intended behaviour.
>> My second question is if there’s way to make vagrant execute a
>> multi-machine setup with the definition in the embedded Vagrantfile, so
>> that a user can use a simple default generated Vagrantfile.
>>
>> --
>> 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/hashicorp/vagrant/issues
>> Discuss: https://discuss.hashicorp.com/c/vagrant/24
>> ---
>> 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/2f2ecef8-a895-4b80-80a1-65aa6dc29f23n%40googlegroups.com
>> <https://groups.google.com/d/msgid/vagrant-up/2f2ecef8-a895-4b80-80a1-65aa6dc29f23n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/CAHqq0ewm%2BNdY43yfGov2rj1FpHCXLk-4kJ2F_uUJ76LBFHf2Uw%40mail.gmail.com
> <https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewm%2BNdY43yfGov2rj1FpHCXLk-4kJ2F_uUJ76LBFHf2Uw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those gu

Re: [vagrant-up] Multi-machine definition not honoured in embedded Vagrantfile

[Alvaro Miranda Aguilera]

Hello

Can you share a zip file with code and instructions ?

Thanks
Alvaro

On Wed, Mar 24, 2021 at 12:03 PM Frits Hoogland 
wrote:

> I am trying to create a vagrant box that launches a cluster of 3 VMs. The
> Vagrantfile to accomplish this works when this definition is in the
> Vagrantfile in the CWD. However, when I move this multi-machine definition
> to the embedded Vagrantfile, vagrant ignores it and creates a default VM,
> ignoring the named machine definitions.
>
> I read the documentation, which doesn’t say anything concrete about this,
> only that multiple Vagrantfiles are merged before starting a vagrant box,
> and that some definitions in the Vagrantfile are added, and some do
> overwrite, which is not very descriptive.
>
> My first question is if this is intended behaviour.
> My second question is if there’s way to make vagrant execute a
> multi-machine setup with the definition in the embedded Vagrantfile, so
> that a user can use a simple default generated Vagrantfile.
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/2f2ecef8-a895-4b80-80a1-65aa6dc29f23n%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ewm%2BNdY43yfGov2rj1FpHCXLk-4kJ2F_uUJ76LBFHf2Uw%40mail.gmail.com.

Re: [vagrant-up] VMware box not listed in Vmware

[Alvaro Miranda Aguilera]

it seems you dnt want to use vagrant

use packer, use vmware-iso, create a fodler and will be a vmx file you can open
or you can use a post processor and convert ovf into ova

once you have the VM into ovf or ova format you can open or import on vmware.

alvaro.

> On Saturday, Jul 18, 2020 at 6:31 PM, Spbb  (mailto:bastiaann...@gmail.com)> wrote:
> So I want the Vmware box to start with the green play button. And NOT with 
> vagrant up.
> Like virtual box.
>
> Op zaterdag 18 juli 2020 om 18:23:48 UTC+2 schreef Spbb:
> >
> > How do I put a Vmware box I made with packer in this interface.
> >
> >
> > Op zaterdag 18 juli 2020 om 08:43:18 UTC+2 schreef kik...@gmail.com:
> > > hello
> > >
> > > not sure i follow where you expect the vm to be registered
> > >
> > > packer will build a vm, and generate a file.box
> > >
> > > then vagrant will create a vm
> > >
> > > if you want the vm that vagrant creates be on the vmware gui, you need to 
> > > enable vmware console
> > >
> > > something like
> > >
> > > Vagrant.configure("2") do |config|
> > > config.vm.box = "my-box"
> > > config.vm.provider "vmware_desktop" do |v|
> > > v.gui = true
> > > end
> > > end
> > >
> > > thanks
> > > alvaro
> > >
> > >
> > > On Sat, Jul 18, 2020 at 12:44 AM Spbb  wrote:
> > > > When I build with packer a vmware.vbox with vagrant the box is not 
> > > > listed in the vmware gui.
> > > >
> > > > How can I archieve this ?
> > > >
> > > >
> > > >
> > > > --
> > > > 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/hashicorp/vagrant/issues
> > > > Discuss: https://discuss.hashicorp.com/c/vagrant/24
> > > > ---
> > > > 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+...@googlegroups.com.
> > > > To view this discussion on the web visit 
> > > > https://groups.google.com/d/msgid/vagrant-up/72e4e24a-7f98-462f-a1ca-61b82ee876b6o%40googlegroups.com
> > > >  
> > > > (https://groups.google.com/d/msgid/vagrant-up/72e4e24a-7f98-462f-a1ca-61b82ee876b6o%40googlegroups.com?utm_medium=email_source=footer).
> > >
> > >
> > > --
> > > 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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 
> (mailto:vagrant-up+unsubscr...@googlegroups.com).
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vagrant-up/940392db-e5b5-42b4-b4e0-9792f19ee0d2n%40googlegroups.com
>  
> (https://groups.google.com/d/msgid/vagrant-up/940392db-e5b5-42b4-b4e0-9792f19ee0d2n%40googlegroups.com?utm_medium=email_source=footer).

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/761d363a-ac99-4a6f-bb6d-cd7e50fb7f35%40Canary.

Re: [vagrant-up] VMware box not listed in Vmware

[Alvaro Miranda Aguilera]

hello

not sure i follow where you expect the vm to be registered

packer will build a vm, and generate a file.box

then vagrant will create a vm

if you want the vm that vagrant creates be on the vmware gui, you need to
enable vmware console

something like

Vagrant.configure("2") do |config|
  config.vm.box = "my-box"
  config.vm.provider "vmware_desktop" do |v|
v.gui = true
  end
end

thanks
alvaro

On Sat, Jul 18, 2020 at 12:44 AM Spbb  wrote:

> When I build with packer a vmware.vbox with vagrant the box is not listed
> in the vmware gui.
>
> How can I archieve this ?
>
>
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/72e4e24a-7f98-462f-a1ca-61b82ee876b6o%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0exEcvjq1m-XmbA0uCjM1iXGZ283afZcK8hjbJkCv4CQ9w%40mail.gmail.com.

Re: [vagrant-up] Not Found The requested URL was not found on this server. Apache/2.4.29 (Ubuntu) Server at localhost Port 9080

[Alvaro Miranda Aguilera]

vagrant is creating the VM and is running the script, so at this stage
feels more a question on apache configuration.


whats the content of the folder /vagrant in the vm?

vagrant ssh

ls -al /vagrant

you need to ensure you have a index.html file that can be served

alvaro



On Sun, Jul 12, 2020 at 7:45 AM Vivek 
wrote:

> I started a ubuntu vm via vagrant. Fine the vagrantfile below. And the
> apache.sh(placed inside of a folder named provision) file to provision
> apache also follow.
>
> I get the get the following error after I launch my vm.
>
> Not Found
> The requested URL was not found on this server.
>
> Apache/2.4.29 (Ubuntu) Server at localhost Port 9080
>
> I have seen quite a few posts for this, but could not find a solution so
> far. Please help.
>
> As per this video , I have
> to modify /etc/apache2/apache2.conf, but I am not sure what I should add to
> the config for my simple case.
>
> The Vagrantfile
>
> # -*- mode: ruby -*-
> # vi: set ft=ruby :
>
> Vagrant.configure("2") do |config|
>   config.vm.box = "bento/ubuntu-18.04"
>
>   config.vm.synced_folder '.', '/vagrant'
>
>   config.vm.network "forwarded_port", guest: 80, host: 9080 #, host_ip:
> "127.0.0.1"
>
>   config.vm.provision "apache", type: "shell", path:
> "provision/apache.sh", privileged: true
>   # vagrant up --provision-with=apache
>
> end
>
> Now the apache.sh provisioning file
>
> #!/usr/bin/env bash
>
> # sodo is not needed because Vagrant will run the script as root, so there
> is no need to actually use sudo.
>
> # We are announcing to the user
> echo "Installing apache ..."
>
> apt-get update
> apt-get install -y apache2
> rm -rf /var/www
> ln -fs /vagrant /var/www
>
> Finally the screen shot of the error that I am getting after launching the
> vm with vagrant up command
>
> [image: TheRequestedUrlNotFound.jpg]
>
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/a21f7aa0-9ac1-412f-9054-a2d322573bc6o%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ez3mCELp8kcE2JonBQ3Hy0EazgcMot1h-k55GdMWFvTaQ%40mail.gmail.com.

Re: [vagrant-up] Vagrant can't connect to guest VM

[Alvaro Miranda Aguilera]

hello

try a different box

if the issue stills happen, quick question.
Are you on any VPN or corporate network?

Have you tried disabling as a test the Firewall of Windows?



On Tue, Jun 23, 2020 at 8:08 PM Ron Trunk  wrote:

> Running:
> Virtualbox 6.1.10 r138449 (Qt5.6.2)
> Vagrant 2.2.9
> Win 10 enterprise V1809
>
> I create a VM using ubuntu/trusty64
>
> The VM gets downloaded and created.  I can see in the console that the
> guest VM starts up and gets to the login prompt.
> But vagrant never connects.  It sits at  "default: SSH auth method:
> private key" until it times out.  the guest VM is operational -- I can log
> in from the console
>
> But I can't ssh:
> >ssh vagrant@127.0.0.1 -p 
> ssh: connect to host 127.0.0.1 port : Connection refused
>
> Any advice would be greatly appreciated.
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/f84ba2dd-81c0-40c4-a159-d94e6b13c1f8o%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ewrrTajD0%3DaMK7_iKWY3aGtwnDF%3D2ZtiScCo1RPFE%3D6ig%40mail.gmail.com.

Re: [vagrant-up] vagrant on windows 10 and centos 8 machines

[Alvaro Miranda Aguilera]

hello

you can't have the same network over 2 different network cards

the network on eth0 is like that and used for nat, access out

if you use different network it will work

192.168.NN.XX

10.10.NN.XX

Thanks
Alvaro

On Tue, Jun 2, 2020 at 12:51 AM Mario G  wrote:

> Hello
> I am starting with vagrant
>
> I am trying to set a multi-machine setup
> i have a few questions.
> first the network configuration in not working on the bento/centos-8.1 box
> the network i add it only added as eth1 eth0 is always the same ip
> 10.0.2.15, the windows host is 10.0.2.2
> so i can reach then separately by ssh but they do not communicate with
> each other
>
> this is the relevant session from the vagrant files:
>
>
> Vagrant.configure("2") do |config|
>   # The most common configuration options are documented and commented
> below.
>   # For a complete reference, please see the online documentation at
>   # https://docs.vagrantup.com.
>
>   # Every Vagrant development environment requires a box. You can search
> for
>   # boxes at https://vagrantcloud.com/search.
>   config.vm.define "ansible" do |ansible|
> ansible.vm.box = "bento/centos-8.1"
> ansible.vm.hostname = "ansible"
> ansible.vm.network "private_network", ip: "10.0.2.10"
>   end
>
>   config.vm.define "ldap" do |ldap|
> ldap.vm.box = "bento/centos-8.1"
> ldap.vm.hostname = "ldap"
> ldap.vm.network "private_network", ip: "10.0.2.100"
>   end
>
>
> this is the network configuration
>
> [vagrant@ansible ~]$ ip a
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group
> default qlen 1000
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
>valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
>valid_lft forever preferred_lft forever
> 2: eth0:  mtu 1500 qdisc fq_codel state
> UP group default qlen 1000
> link/ether 52:54:00:72:fe:6e brd ff:ff:ff:ff:ff:ff
> inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic noprefixroute
> eth0
>valid_lft 86077sec preferred_lft 86077sec
> inet6 fe80::5054:ff:fe72:fe6e/64 scope link
>valid_lft forever preferred_lft forever
> 3: eth1:  mtu 1500 qdisc fq_codel state
> UP group default qlen 1000
> link/ether 08:00:27:91:b2:04 brd ff:ff:ff:ff:ff:ff
> inet 10.0.2.10/24 brd 10.0.2.255 scope global noprefixroute eth1
>valid_lft forever preferred_lft forever
> inet6 fe80::a00:27ff:fe91:b204/64 scope link
>valid_lft forever preferred_lft forever
> [vagrant@ansible ~]$ ip route show
> default via 10.0.2.2 dev eth0 proto dhcp metric 100
> 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 metric 100
> 10.0.2.0/24 dev eth1 proto kernel scope link src 10.0.2.10 metric 101
>
>
> pinging the other vm does not work.. because it also has eth0 with the
> same IP
>
> the hypervisor is virtualbox
> I guress that is the default and I do not have to add any virtualbox
> configuration for network? I have not found any information
>
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/8c5e2fe3-9385-479f-9362-248b8c09db07%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ezSL1xLCQRk-q7KFgrmAEfAXXsEE-E3XjQcLfJ6chyrGA%40mail.gmail.com.

Re: [vagrant-up] Vagrant user's pub ssh key location?

[Alvaro Miranda Aguilera]

hello

you can use vagrant ssh-config to see the keys that can be used to login

hope this helps

alvaro

On Mon, Jun 8, 2020 at 8:12 AM Makrand  wrote:

> Hello All,
>
> Where excatly is public key (which is stored in authorized key under .ssh
> in vagrant launched VM) for vagrant user is stored on the localhost?
>
> I can see below for an example VM
>
>
> makrand@mint-gl63:~/vagrant_ssd/ubuntu18/.vagrant/machines/ubuntu-rke/virtualbox$
> pwd
> /home/makrand/vagrant_ssd/ubuntu18/.vagrant/machines/ubuntu-rke/virtualbox
> makrand@mint-gl63:~/vagrant_ssd/ubuntu18/.vagrant/machines/ubuntu-rke/virtualbox$
> ls -l
> total 76
> -rw-rw-r-- 1 makrand makrand40 Jun  7 16:05 action_provision
> -rw-rw-r-- 1 makrand makrand10 Jun  8 11:19 action_set_name
> -rw-rw-r-- 1 makrand makrand   148 Jun  8 11:19 box_meta
> -rw-rw-r-- 1 makrand makrand 4 Jun  7 16:04 creator_uid
> -rw-rw-r-- 1 makrand makrand36 Jun  7 16:04 id
> -rw-rw-r-- 1 makrand makrand32 Jun  7 16:04 index_uuid
> -rw--- 1 makrand makrand  1679 Jun  7 16:05 private_key
> -rw-rw-r-- 1 makrand makrand   138 Jun  8 11:19 synced_folders
> -rw--- 1 makrand makrand 40455 Jun  8 11:19
> ubuntu-bionic-18.04-cloudimg-console.log
> -rw-rw-r-- 1 makrand makrand34 Jun  7 16:04 vagrant_cwd
>
>
> I am wondering how does public is set into .ssh folder onto VM? Is it
> created on fly against above private key each time VM is provisioned?
>
>
> I am asking this because - I am setting up RKE (Rancher Kubernetes Engine)
> on single vagrant launched VM. While I am building the config to launch K8
> clsuterit is asking me to set  - *SSH Private Key Path of host*
>
> Normally for setting up the passwordless login - one generates both pub
> and private key & then moves pub key from localhost to deisnation machine.
> I don't see
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/250f6600-2ef0-4e56-a04a-51a0cf10ef78o%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0eycpcDG7DHtnN-anbsXgQbeb6Nyd3Li%3DSxz-CcBQwq5Fw%40mail.gmail.com.

Re: [vagrant-up] Help with getting a Vagrantfile up and running on Windows 10 (It is running on a Linux OS!)

[Alvaro Miranda Aguilera]

So, hyper-v network is different from what virtualbox does, so i am not
sure the project will be useful just changing hyper-v where it was
virtualbox

what you can try is either create a VM or use WSL2 linux

and replace this line

force_host_vm = TRUE

to
force_host_vm = FALSE

And if you run vagrant from a linux machine, it should just create the
docker containers without the need to create a linux vm.

i would start there

once you get there, my suggestion will be invest some time slowly

create a vagrant project that create a linux vm on hyperv
add a docker container
port this project to your own install

but if you have time constraints, run this from a linux box should be the
faster path.

alvaro

On Fri, May 22, 2020 at 8:46 PM Frank Gunseor  wrote:

> Hello everyone,
>
> I am relatively new to Vagrant and Docker.
>
> I have the above Vagrantfile(s) running on a Linux OS on my laptop just
> fine.
>
> I would like to get it running on my Windows 10 desktop system due to more
> RAM and faster CPUs.
>
> It appears to me that my problem is that the box(es) related to this
> multi-container, multi-VM system are specific to VirtualBox.
>
> VirtualBox does not function (yet?) on Windows 10 because Docker requires
> Hyper-V to be enabled for it to functional, although VirtualBox claims
> built-in functionality with Hyper-V the consensus on the forums, support,
> etc. and that I can confirm is not ready, yet.
>
> So, I would appreciate any help that anyone can provide to help me get
> this "system" to run on Widows 10.
>
> Please note that Docker and Vagrant BOTH are running just fine on my
> Windows 10 desktop.
>
> This is the error message I get that is basically the same for every
> container and VM:
>
> An error occurred while executing the action on the 'dev'
> machine. Please handle this error then try again:
>
> There was an error while executing `VBoxManage`, a CLI used by Vagrant
> for controlling VirtualBox. The command and stderr is shown below.
>
> Command: ["startvm", "b8d0a299-220a-4a52-b6c0-4c967ed980d5", "--type",
> "headless"]
>
> Stderr: VBoxManage.exe: error: WHvCapabilityCodeHypervisorPresent is
> FALSE! Make sure you have enabled the 'Windows Hypervisor Platform'
> feature. (VERR_NEM_NOT_AVAILABLE).
> VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
> VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component
> ConsoleWrap, interface IConsole
>
> I can provide much more if needed.
>
> Is there anyway to add the Hyper-V provider to this box? If so, how?
>
> Any help is appreciated.
>
> Frank Gunseor
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/b40507a2-8a4f-415b-a471-d3192b936a5b%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0exGw%2BrWKgKey-Z_ooC4XcG4F-u42ML4bxcGK9Ca8Coo2w%40mail.gmail.com.

Re: [vagrant-up] Vagrant a portable app?

[Alvaro Miranda Aguilera]

hello

Do you know if those desktops have virtualbox installed?

are you local admin to create networks if needed ?

i think a good approach will be check with the IT folks that manage those
environments.

Vagrant defaults to install to C:\HashiCorp, you could try to install to
pendrive on one computer and see if works in other.

alvaro

On Wed, May 13, 2020 at 7:27 PM Remo Gaggi  wrote:

> I use vagrant 2.2.9 on Windows 10.
>
> I may be mistaken, but I don't think it adds entries to the registry.
>
> Therefore, can it be configured to run as a portable app so that it can
> run from a thumb drive?
>
> I work in a "floater" environment where workstations are shared, and I
> want to ensure I always have the app at my disposal no matter where I'm
> stationed for a particular day.
>
> Thanks,
> Remo
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/93cb0140-ac9f-4f4a-8a16-8d02a29fa8af%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ewsHarW-Aa%2BUBkOkmM8m-kpYKs8LDPfCCtJg9WROL2oxg%40mail.gmail.com.

Re: [vagrant-up] Unable to join HyperV node to swarm

[Alvaro Miranda Aguilera]

hello

attached what works

were some error on the script and removed yum upgrade.
better not do that as may break modules in the kernel.

default: Installed:

default:   awscli.noarch 0:1.14.28-5.el7_5.1


default:

default: Dependency Installed:

default:   PyYAML.x86_64 0:3.10-11.el7


default:   jbigkit-libs.x86_64 0:2.0-11.el7


default:   libjpeg-turbo.x86_64 0:1.2.90-8.el7


default:   libtiff.x86_64 0:4.0.3-32.el7


default:   libwebp.x86_64 0:0.3.0-7.el7


default:   libyaml.x86_64 0:0.1.4-11.el7_0


default:   python-backports.x86_64 0:1.0-8.el7


default:   python-backports-ssl_match_hostname.noarch 0:3.5.0.1-1.el7


default:   python-cffi.x86_64 0:1.6.0-5.el7


default:   python-dateutil.noarch 0:1.5-7.el7


default:   python-docutils.noarch 0:0.11-0.3.20130715svn7687.el7


default:   python-enum34.noarch 0:1.0.4-1.el7


default:   python-idna.noarch 0:2.4-1.el7


default:   python-ipaddress.noarch 0:1.0.16-2.el7


default:   python-pillow.x86_64 0:2.0.0-20.gitd1c6db8.el7_7


default:   python-ply.noarch 0:3.4-11.el7


default:   python-pycparser.noarch 0:2.14-1.el7


default:   python-s3transfer.noarch 0:0.1.13-1.el7.0.1


default:   python-setuptools.noarch 0:0.9.8-7.el7


default:   python-six.noarch 0:1.9.0-2.el7


default:   python2-cryptography.x86_64 0:1.7.2-2.el7


default:   python2-pyasn1.noarch 0:0.1.9-7.el7


default:

default: Complete!

default: Python 3.6.8

default: aws-cli/1.14.28 Python/2.7.5 Linux/3.10.0-957.12.2.el7.x86_64
botocore/1.8.35

[kikitux:*~/Downloads/x*]



On Mon, May 11, 2020 at 6:08 PM kathir  wrote:

> Hi Please find the attached vagrant file & script file for your reference
>
> As i am getting the error
> Thanks & Regards,
> Kathirvel G
>
>
> On Wed, May 6, 2020 at 7:10 PM Alvaro Miranda Aguilera 
> wrote:
>
>> if you share the script we can have a look
>>
>> Xwindows
>> https://en.wikipedia.org/wiki/X_Window_System
>>
>>
>>
>> On Tue, May 5, 2020 at 11:29 AM kathir  wrote:
>>
>>> yes that's correct
>>>
>>> I already did that individual commands are running in ssh, but not able
>>> run through vagrant external script provisioning
>>>
>>> i got the above error, is it related guest addition or what is that X ?
>>>
>>> Thanks & Regards,
>>> Kathirvel G
>>>
>>>
>>> On Tue, May 5, 2020 at 10:07 AM Alvaro Miranda Aguilera <
>>> kiki...@gmail.com> wrote:
>>>
>>>> You don't seems to have an X running.
>>>>
>>>> This usually happens if you run a graphical application or an
>>>> application that need graphics
>>>>
>>>> just ssh to the machine, copy and run the script to see if you see the
>>>> same error.
>>>>
>>>> if you hit the same error, the error is coming from the scripts and the
>>>> way is being run and not vagrant.
>>>>
>>>> Thanks
>>>> Alvaro
>>>>
>>>> On Mon, Apr 27, 2020 at 11:52 AM kathir 
>>>> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> When i tried to use vagrant file provisioning using external shell
>>>>> script, i ended up to look into log file as it says
>>>>>
>>>>>   Could not find the X.Org or XFree86 Window System, skipping
>>>>>
>>>>> Please suggest
>>>>> Thanks & Regards,
>>>>> Kathirvel G
>>>>>
>>>>>
>>>>> On Mon, Apr 27, 2020 at 10:00 AM Alvaro Miranda Aguilera <
>>>>> kiki...@gmail.com> wrote:
>>>>>
>>>>>> so, make sure you can ping both IP from both host
>>>>>>
>>>>>> on machine1
>>>>>> - ping local
>>>>>> - ping remote
>>>>>>
>>>>>> on machine2
>>>>>> - ping local
>>>>>> - ping remote
>>>>>>
>>>>>> if one fails, then you should focus on that first.
>>>>>>
>>>>>> As you are using hyper-v, I can't help much, but basically you may
>>>>>> want to see way to give to the VMs an IP from your network.
>>>>>>
>>>>>> Alvaro.
>>>>>>
>>>>>> On Fri, Apr 24, 2020 at 3:10 PM DC 
>>>>>> wrote:
>>>>>>
>>>>>>> I am using the latest vagrant version running on my windows 10
>>>>>>> professional x

Re: [vagrant-up] Vagrant: Newbee troubleshooting - Provision - Cannot uninstall requirement

[Alvaro Miranda Aguilera]

vagrant is just running an script here

so the best will ask for guidance from the app you are trying to use

alvaro.

On Tue, May 12, 2020 at 12:11 PM SColeman  wrote:

> Vagrant has been running fine for a while for me.  I made some changes to
> some code and then provision the changes (in the way that I always do).
> While the provision is running however  I get the following error:
>
>
> *strats: Cannot uninstall requirement condor, not installed*
> *strats: Cannot uninstall requirement merlin, not installed*
> *The SSH command responded with a non-zero exit status. Vagrant*
> *assumes that this means the command failed. The output for this command*
> *should be in the log above. Please read the output to determine what*
> *went wrong.*
>
> Condor and merlin are the names of python projects that I have created.
> Please see the attached for complete provision output.
>
> Do I need to manually uninstall the projects, upgrade Vagrant or something
> else?
>
>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/f2b04a9c-64bc-449a-a2d2-c6d0fd2a9875%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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAHqq0ezjBg9LzNw%3D8yWuWuf2_Vs9UDGC5AK-RC--ZQmzuRebeA%40mail.gmail.com.

Re: [vagrant-up] Re: Specifying use of the new "NAT Network" option in Vagrantfile

[Alvaro Miranda Aguilera]

hello

you did reply to a email from 2015, i would suggest send a new email to the
group and describe what you need or how we can help

vagrant and virtualbox have changed a lot since 2015 so things may be
different

alvaro

On Thu, May 7, 2020 at 9:22 AM st3b4n 4lvin0  wrote:

> Peter,
> Difficult to find material how to configure 'Nat Network' with virtual
> box, when I add private network to vagrant file it added in one machine but
> other one failed the first time. Any procedure that I can study to
> understand and configured.
>
> On Wednesday, July 15, 2015 at 5:19:58 PM UTC-5, Peter Ferriola wrote:
>>
>> The solution you present does work, but does not utilize a feature
>> VirtualBox added to create a NAT network behind which all the VMs in a
>> given NAT network reside.  For example, I've used it to create (outside of
>> Vagrant) a Puppet test environment with a Puppet Master and five clients
>> without any particular complexity to the configuration.  Just
>> straightforward IPs and they can all access each other and the Internet
>> just fine, with a single IP per system.  Much closer to the reality of the
>> production environments some tests are meant to reflect.
>>
>> Your solution does work, but it adds complexity to what should be a very
>> simple setup, and what Oracle has already integrated into VirtualBox itself.
>>
>> On Tuesday, May 19, 2015 at 4:36:48 PM UTC-7, Alvaro Miranda Aguilera
>> wrote:
>>>
>>> Hello,
>>>
>>> Maybe I am missing something, but I think with normal networks you can
>>> do the same..
>>>
>>> What do you need that the normal vagrant networking doesn't provide?
>>>
>>> Check this:
>>>
>>> http://en.wikibooks.org/wiki/RAC_Attack_-_Oracle_Cluster_Database_at_Home/RAC_Attack_Automation#/media/File:RA_Arquitecture_step2.png
>>>
>>>
>>> Because this is how you usually work with Vagrant and virtualbox:
>>>
>>> Out of the box, you get the normal nat for eth0 connection
>>>
>>> Then, using a mix of shell provisioner and network configuration you can
>>>
>>> add a 2nd interface (any config.vm.network line create a new nic on top
>>> of eth0.. you can't change eth0 this way)
>>> remove the default gw that goes over the normal nat on eth0
>>> add a new default gw over the eth1 nic
>>>
>>> That is how you can do a multi vm setup that talk internally and
>>> optionally use this eth1 network for routing too.
>>>
>>>
>>> So, in the clusters I do I end with something like this:
>>>
>>>
>>> http://en.wikibooks.org/wiki/RAC_Attack_-_Oracle_Cluster_Database_at_Home/RAC_Attack_Automation#/media/File:RA_Arquitecture_step2.png
>>>
>>> and you can also forward a port to each VM
>>>
>>> So, not sure if that particular natservices is really needed,
>>>
>>> Alvaro
>>>
>>> On Wed, May 20, 2015 at 9:05 AM, Chris Almond 
>>> wrote:
>>>
>>>> More clarification. For the custom NAT Network definition shown below
>>>> (vbox preferences -> network), how do I specify using in Vagrantfile?
>>>>
>>>> Would it be something like this?  config.vm.network :forwarded_port, 
>>>> :adapter
>>>> => "2"  (...for the second (custom) NAT adapter?)
>>>>
>>>> *vbox adapter type:  vagrant network type:*
>>>> "Host-only Adapter" =  "private_network"
>>>> "Bridged Adapter"   =  "public_network"
>>>>  "NAT"  =  "forwarded_port"
>>>> *?--> "NAT Network1" =   "?"*
>>>>
>>>>
>>>> <https://lh3.googleusercontent.com/-4lHYU-VGNrQ/VVui7PN8bxI/AI8/rkc_Kd23Vv4/s1600/natnetwork1.jpg>
>>>>
>>>>
>>>> On Tuesday, May 19, 2015 at 1:21:42 PM UTC-7, Chris Almond wrote:
>>>>>
>>>>> Can anyone share examples that show how to specify use of the new "NAT
>>>>> Network" option for network type?
>>>>>
>>>>> Virtualbox doc ref: *6.4. Network Address Translation Service
>>>>> (experimental)*
>>>>> https://www.virtualbox.org/manual/ch06.html#network_nat_service
>>>>>
>>>>> The goal is to use Vagrant to provision a cluster of boxes, all
>>>>> members of the same custom defined NAT service, with DHCP providing 
&g

Re: [vagrant-up] Virtual Box bridged network and port forwarding VAGRANT

[Alvaro Miranda Aguilera]

i would suggest:

compare the output of route print when works and when doesnt

run the commands you have for route one at the time, and check route print

perhaps there is some step missed, some route needed to be clean or
something

alvaro


On Thu, May 7, 2020 at 2:16 AM Yayaoui Namoussi  wrote:

> Well i think its cause i need a default route to the router
> 0.0.0.0 10.0.2.20.0.0.0 UG0  00
> eth0
> 10.0.2.00.0.0.0 255.255.255.0   U 0  00
> eth0
> 192.168.1.0 0.0.0.0 255.255.255.0   U 0  00
> eth1
>
> when i add
> 0.0.0.0192.168.1.254 it start working,but i dont understund
> why its not add by
>config.vm.provision "shell", run: "always", inline: "route add default
> gw 192.168.1.254"
>
> Le dimanche 5 avril 2020 19:52:17 UTC+2, Alvaro Miranda Aguilera a écrit :
>>
>> it shoudl work without port forward
>>
>> whats the output from the vm of
>>
>> route -n
>> ip addr
>>
>> as long default gw goes to the router it should work
>>
>>
>>
>> On Fri, Apr 3, 2020 at 10:08 PM Yayaoui Namoussi 
>> wrote:
>>
>>> <https://i.gyazo.com/68dfcd78c251d7182009c766c7507def.png>
>>> This is my network :
>>>
>>> Le vendredi 3 avril 2020 21:14:31 UTC+2, Alvaro Miranda Aguilera a
>>> écrit :
>>>>
>>>> if you comment out and try from the home network, does work?
>>>>
>>>> do you have how to test ?
>>>>
>>>> you dont need port forward if the VM is having a public IP on the
>>>> network
>>>>
>>>> On Fri, Apr 3, 2020 at 5:22 PM Yayaoui Namoussi 
>>>> wrote:
>>>>
>>>>> Hey guys i'm having serious problme with to portforward my port 5060
>>>>> i'm stuck on it since 1 week :(
>>>>> the probleme is i want to portforward the port 5060 on my bridge
>>>>> network not in nat so naturaly i did this
>>>>>
>>>>>
>>>>>   config.vm.network "public_network", :bridge => "Realtek PCIe
>>>>> 2.5GbE Family Controller", :ip => "192.168.1.117"
>>>>>
>>>>>
>>>>> ###DEFAULT ROUTER##
>>>>> config.vm.provision "shell",
>>>>> run: "always",
>>>>> inline: "route add default gw 192.168.1.254"
>>>>>
>>>>>  config.vm.provision "shell",
>>>>> run: "always",
>>>>> inline: "eval `route -n | awk '{ if ($8 ==\"eth0\" && $2 !=
>>>>> \"0.0.0.0\") print \"route del default gw \" $2; }'`"
>>>>>   config.vm.network "forwarded_port", :adapter=>2, guest: 5060,host:
>>>>> 5060, protocol: "udp"
>>>>>
>>>>>
>>>>> Then when i do vagrant reload i have this
>>>>>
>>>>> default: VirtualBox adapter #2 not configured as "NAT".
>>>>> Skipping port
>>>>>
>>>>>
>>>>> in my router i did port forwarding like this 192.168.1.117 / UDP / ALL
>>>>> IP / 5060 / 5060
>>>>> and still when i try to check open port through internet its says the
>>>>> port is close
>>>>>
>>>>> --
>>>>> 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/d647b519-e8f0-4d38-a738-3398e4eb9e96%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/vagrant-up/d647b519-e8f0-4d38-a738-3398e4eb9e96%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
&g

Re: [vagrant-up] NFS Sharing from host to Vagrant VM !!

[Alvaro Miranda Aguilera]

there is a nfs server on  192.168.121.1 ?

can you mount on the guest manually  192.168.121.1:/root/hlinux-
tools/netinst-iso
?


alvaro

On Tue, May 5, 2020 at 4:24 PM Ibrahim Vanak 
wrote:

> The issue is, while running “vagrant up” I am trying to do NFS mount from
> host to Vagrant VM. It’s failing to do so with the following error:
>
> ==> default: Mounting NFS shared folders...
>
> The following SSH command responded with a non-zero exit status.
>
> Vagrant assumes that this means the command failed!
>
>
>
> mount -o vers=4 192.168.121.1:/root/hlinux-tools/netinst-iso /vagrant
>
>
>
> Stdout from the command:
>
>
>
>
>
>
>
> Stderr from the command:
>
>
>
> mount.nfs: access denied by server while mounting 192.168.121.1:
> /root/hlinux-tools/netinst-iso
>
>
> My host VM is unbuntu 18.04 and vagrant VM would be debian Jessie.
>
>
> Snippet of NFS sharing code from Vagrant file:
>
>
> *  config.vm.synced_folder "./vagrantfolder", "/home/vagrant/output",*
>
> *nfs: true,*
>
> *linux__nfs_options: ['rw','no_subtree_check','all_squash','async']*
>
>
>
> *  config.vm.synced_folder "./vagrantfolder/repo",
> "/var/www/hLinuxArchive",*
>
> *nfs: true,*
>
> *linux__nfs_options: ['rw','no_subtree_check','all_squash','async']*
>
> --
> 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/1de9e302-83d1-4324-b1a8-373123fb3efe%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/CAHqq0ezdAyu%2Bt5YQU%3DYUAJkb6h3EB62CoBTTLfCFOF9tTuO4Zw%40mail.gmail.com.

Re: [vagrant-up] Unable to join HyperV node to swarm

[Alvaro Miranda Aguilera]

if you share the script we can have a look

Xwindows
https://en.wikipedia.org/wiki/X_Window_System



On Tue, May 5, 2020 at 11:29 AM kathir  wrote:

> yes that's correct
>
> I already did that individual commands are running in ssh, but not able
> run through vagrant external script provisioning
>
> i got the above error, is it related guest addition or what is that X ?
>
> Thanks & Regards,
> Kathirvel G
>
>
> On Tue, May 5, 2020 at 10:07 AM Alvaro Miranda Aguilera 
> wrote:
>
>> You don't seems to have an X running.
>>
>> This usually happens if you run a graphical application or an application
>> that need graphics
>>
>> just ssh to the machine, copy and run the script to see if you see the
>> same error.
>>
>> if you hit the same error, the error is coming from the scripts and the
>> way is being run and not vagrant.
>>
>> Thanks
>> Alvaro
>>
>> On Mon, Apr 27, 2020 at 11:52 AM kathir  wrote:
>>
>>> Hi
>>>
>>> When i tried to use vagrant file provisioning using external shell
>>> script, i ended up to look into log file as it says
>>>
>>>   Could not find the X.Org or XFree86 Window System, skipping
>>>
>>> Please suggest
>>> Thanks & Regards,
>>> Kathirvel G
>>>
>>>
>>> On Mon, Apr 27, 2020 at 10:00 AM Alvaro Miranda Aguilera <
>>> kiki...@gmail.com> wrote:
>>>
>>>> so, make sure you can ping both IP from both host
>>>>
>>>> on machine1
>>>> - ping local
>>>> - ping remote
>>>>
>>>> on machine2
>>>> - ping local
>>>> - ping remote
>>>>
>>>> if one fails, then you should focus on that first.
>>>>
>>>> As you are using hyper-v, I can't help much, but basically you may want
>>>> to see way to give to the VMs an IP from your network.
>>>>
>>>> Alvaro.
>>>>
>>>> On Fri, Apr 24, 2020 at 3:10 PM DC  wrote:
>>>>
>>>>> I am using the latest vagrant version running on my windows 10
>>>>> professional x64. I configured my Network device to share the connection
>>>>> with my internal virtual switch (HyperV). Everything seams okay and I can
>>>>> bring up my VM without any issues. I am using the following box
>>>>> (generic/ubuntu1804).
>>>>>
>>>>> The problem that I have is that once that my host gets the assigned
>>>>> the admin role, after run "docker swarm init", I tried to add the
>>>>> Hypervisor as a Worker node and I seems like is docker can not see it :-/.
>>>>>
>>>>> *These are the steps that I followed:*
>>>>>
>>>>> # Bring up w1 (My vagrantfile will handle the provider,etc) IP =
>>>>> 192.163.135.199
>>>>> *vagrant up w1*
>>>>>
>>>>> # host machine
>>>>> *docker init swarm*
>>>>> *To add a worker to this swarm, run the following command:*
>>>>>
>>>>> *docker swarm join --token
>>>>> SWMTKN-1-36gi398mfzkq8q9f4qt6u5wll7xv88a4u0osv8rpofmmvknunn-91ogycjru6p29p44f7iam63il
>>>>>  *
>>>>> 192.163.135.197*:2377*
>>>>>
>>>>> *To add a manager to this swarm, run 'docker swarm join-token manager'
>>>>> and follow the instructions.*
>>>>>
>>>>> # Switch to Worker
>>>>> *$env:DOCKER_HOST="192.163.135.199"*
>>>>>
>>>>> # I verified that docker can see this node
>>>>>
>>>>> *docker info*
>>>>>
>>>>> # docker shows Name: w1 :-)
>>>>>
>>>>> # Join the current node as worker
>>>>> *docker swarm join --token
>>>>> SWMTKN-1-36gi398mfzkq8q9f4qt6u5wll7xv88a4u0osv8rpofmmvknunn-91ogycjru6p29p44f7iam63il
>>>>>  192.163.135.197:2377
>>>>> <http://192.163.135.197:2377>*
>>>>> *Error response from daemon: Timeout was reached before node joined.
>>>>> The attempt to join the swarm will continue in the background. Use the
>>>>> "docker info" command to see the current swarm status of your node.*
>>>>>
>>>>> *Troubleshooting:*
>>>>>
>>>>> I ping the VM and the host is able to see it, but if  *I try to ping
>>>>> the host from the VM, it failed* :-/. I a

Re: [vagrant-up] Unable to join HyperV node to swarm

[Alvaro Miranda Aguilera]

You don't seems to have an X running.

This usually happens if you run a graphical application or an application
that need graphics

just ssh to the machine, copy and run the script to see if you see the same
error.

if you hit the same error, the error is coming from the scripts and the way
is being run and not vagrant.

Thanks
Alvaro

On Mon, Apr 27, 2020 at 11:52 AM kathir  wrote:

> Hi
>
> When i tried to use vagrant file provisioning using external shell script,
> i ended up to look into log file as it says
>
>   Could not find the X.Org or XFree86 Window System, skipping
>
> Please suggest
> Thanks & Regards,
> Kathirvel G
>
>
> On Mon, Apr 27, 2020 at 10:00 AM Alvaro Miranda Aguilera <
> kiki...@gmail.com> wrote:
>
>> so, make sure you can ping both IP from both host
>>
>> on machine1
>> - ping local
>> - ping remote
>>
>> on machine2
>> - ping local
>> - ping remote
>>
>> if one fails, then you should focus on that first.
>>
>> As you are using hyper-v, I can't help much, but basically you may want
>> to see way to give to the VMs an IP from your network.
>>
>> Alvaro.
>>
>> On Fri, Apr 24, 2020 at 3:10 PM DC  wrote:
>>
>>> I am using the latest vagrant version running on my windows 10
>>> professional x64. I configured my Network device to share the connection
>>> with my internal virtual switch (HyperV). Everything seams okay and I can
>>> bring up my VM without any issues. I am using the following box
>>> (generic/ubuntu1804).
>>>
>>> The problem that I have is that once that my host gets the assigned the
>>> admin role, after run "docker swarm init", I tried to add the Hypervisor as
>>> a Worker node and I seems like is docker can not see it :-/.
>>>
>>> *These are the steps that I followed:*
>>>
>>> # Bring up w1 (My vagrantfile will handle the provider,etc) IP =
>>> 192.163.135.199
>>> *vagrant up w1*
>>>
>>> # host machine
>>> *docker init swarm*
>>> *To add a worker to this swarm, run the following command:*
>>>
>>> *docker swarm join --token
>>> SWMTKN-1-36gi398mfzkq8q9f4qt6u5wll7xv88a4u0osv8rpofmmvknunn-91ogycjru6p29p44f7iam63il
>>>  *
>>> 192.163.135.197*:2377*
>>>
>>> *To add a manager to this swarm, run 'docker swarm join-token manager'
>>> and follow the instructions.*
>>>
>>> # Switch to Worker
>>> *$env:DOCKER_HOST="192.163.135.199"*
>>>
>>> # I verified that docker can see this node
>>>
>>> *docker info*
>>>
>>> # docker shows Name: w1 :-)
>>>
>>> # Join the current node as worker
>>> *docker swarm join --token
>>> SWMTKN-1-36gi398mfzkq8q9f4qt6u5wll7xv88a4u0osv8rpofmmvknunn-91ogycjru6p29p44f7iam63il
>>>  192.163.135.197:2377
>>> <http://192.163.135.197:2377>*
>>> *Error response from daemon: Timeout was reached before node joined. The
>>> attempt to join the swarm will continue in the background. Use the "docker
>>> info" command to see the current swarm status of your node.*
>>>
>>> *Troubleshooting:*
>>>
>>> I ping the VM and the host is able to see it, but if  *I try to ping
>>> the host from the VM, it failed* :-/. I am guessing that it has to do
>>> with the way that I configured the internal virtual switch :-/. Any
>>> recommendation?
>>>
>>>
>>> --
>>> 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/aa877eb8-2fd8-4e9c-b9ec-f3b586794631%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/aa877eb8-2fd8-4e9c-b9ec-f3b586794631%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> Alvaro
>>
>> --
>> This mailing list is governed under th

Re: [vagrant-up] Vagrant keeping my disks awake

[Alvaro Miranda Aguilera]

What about you mount in the guest some remote filesystem ??

in that way will be accessed only when needed.

without much information about how your pc looks like, boot disk,
filesystem layout, will be a lot of guessing.

So i would take the simple route and use a filesystem to the VM.

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

Re: [vagrant-up] Unable to join HyperV node to swarm

[Alvaro Miranda Aguilera]

so, make sure you can ping both IP from both host

on machine1
- ping local
- ping remote

on machine2
- ping local
- ping remote

if one fails, then you should focus on that first.

As you are using hyper-v, I can't help much, but basically you may want to
see way to give to the VMs an IP from your network.

Alvaro.

On Fri, Apr 24, 2020 at 3:10 PM DC  wrote:

> I am using the latest vagrant version running on my windows 10
> professional x64. I configured my Network device to share the connection
> with my internal virtual switch (HyperV). Everything seams okay and I can
> bring up my VM without any issues. I am using the following box
> (generic/ubuntu1804).
>
> The problem that I have is that once that my host gets the assigned the
> admin role, after run "docker swarm init", I tried to add the Hypervisor as
> a Worker node and I seems like is docker can not see it :-/.
>
> *These are the steps that I followed:*
>
> # Bring up w1 (My vagrantfile will handle the provider,etc) IP =
> 192.163.135.199
> *vagrant up w1*
>
> # host machine
> *docker init swarm*
> *To add a worker to this swarm, run the following command:*
>
> *docker swarm join --token
> SWMTKN-1-36gi398mfzkq8q9f4qt6u5wll7xv88a4u0osv8rpofmmvknunn-91ogycjru6p29p44f7iam63il
>  *
> 192.163.135.197*:2377*
>
> *To add a manager to this swarm, run 'docker swarm join-token manager' and
> follow the instructions.*
>
> # Switch to Worker
> *$env:DOCKER_HOST="192.163.135.199"*
>
> # I verified that docker can see this node
>
> *docker info*
>
> # docker shows Name: w1 :-)
>
> # Join the current node as worker
> *docker swarm join --token
> SWMTKN-1-36gi398mfzkq8q9f4qt6u5wll7xv88a4u0osv8rpofmmvknunn-91ogycjru6p29p44f7iam63il
>  192.163.135.197:2377
> *
> *Error response from daemon: Timeout was reached before node joined. The
> attempt to join the swarm will continue in the background. Use the "docker
> info" command to see the current swarm status of your node.*
>
> *Troubleshooting:*
>
> I ping the VM and the host is able to see it, but if  *I try to ping the
> host from the VM, it failed* :-/. I am guessing that it has to do with
> the way that I configured the internal virtual switch :-/. Any
> recommendation?
>
>
> --
> 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/aa877eb8-2fd8-4e9c-b9ec-f3b586794631%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/CAHqq0exgOwL2qZgr6BuYGUixsPHeLs1h%3DwG7rbr9Y0Z-p2Vc%2BQ%40mail.gmail.com.

Re: [vagrant-up] Few newbie questions

[Alvaro Miranda Aguilera]

hi

vagrant will create the vms top to bottom

if you define

client1,2,3
server

it will do server at the end.


If you need to run commands between vms, the best will be use a known ssh
key to be able to just do ssh commands

here is an example I did for a docker swarm cluster

https://github.com/kikitux/swarm-playground

Alvaro.


On Sat, Apr 11, 2020 at 10:24 PM Brian Makin  wrote:

> I'm setting a microk8s cluster.  To join those nodes I have to run a
> command on one node, then run the output of that command on another node.
> How would I set this up?
>
> Is there a way to make one VM wait for another to come up before it starts
> to come up?
> ie: bring up the master, then all the client nodes?
>
> --
> 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/c8166fcb-a0a4-418f-bf6b-54ea6f99c3fd%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/CAHqq0ezRSAoi%3DkPESxMVpXdapT-6r3jb8Udr7eFc%3DSuBcKQbsA%40mail.gmail.com.

Re: [vagrant-up] plugin install vagrant-aws fails on dependency ovirt-engine-sdk 4.4.0: requires Ruby version >= 2.5

[Alvaro Miranda Aguilera]

hello

vagrant uses his own ruby version.

if you want something older, you can check the changelog, and try an older
version

https://releases.hashicorp.com/vagrant/

https://github.com/hashicorp/vagrant/blob/master/CHANGELOG.md#201-november-2-2017

alvaro.

On Mon, Apr 13, 2020 at 6:20 PM Frank Rehwinkel 
wrote:

> $ vagrant plugin install vagrant-aws
>> Installing the 'vagrant-aws' plugin. This can take a few minutes...
>> Vagrant failed to properly resolve required dependencies. These
>> errors can commonly be caused by misconfigured plugin installations
>> or transient network issues. The reported error is:
>> ovirt-engine-sdk requires Ruby version >= 2.5.
>
>
> Running on macOS with vagrant installed via homebrew.
>
> Since the vagrant-aws plugin worked for me last year, two things have
> changed that I can tell.
>
> vagrant went from 2.2.5 to 2.2.7 and after seeing the plugin install step
> failed, and checking through gems and GitHub, I see ovirt-engine-sdk has
> gone from 4.3.0 to 4.4.0 a few days ago, while vagrant-aws hasn't changed
> in well over a year. And the git log for ovirt-engine-sdk-ruby does seem to
> indicate a version in their config went from 2.4 to 2.5 but I can't attest
> that is a ruby version.
>
> I've looked at the vagrant-aws gem and it doesn't rely on ovirt-engine-sdk
> directly but it pulls in fog and iniparse and a few other things. I also
> haven't seen how to specify an older version of a plugin or an older
> version of a dependency of a plugin.
>
> I did find how to use homebrew to pull in an older vagrant, but dropping
> back to 2.2.5 didn't make any difference. The 4.4.0 version of
> ovirt-engine-sdk was still a failing dependency.
>
> Homebrew has my ruby version at 2.7.1 but I've ready vagrant comes with
> its own ruby although I don't see it in the homebrew Casks directory.
>
> Should I be looking at why vagrant doesn't have access to my 2.7.1 ruby or
> how to get back to 4.3.0 of ovirt-engine-sdk or perhaps why
> ovirt-engine-sdk is even needed in my setup? I want to use vagrant to start
> up an aws machine and give me ssh access to it.
>
> Thanks.
>
> --
> 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/d30e9936-81c0-4854-b0a7-38e361c5366d%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/CAHqq0ex%2BN_OU5SPka2%3D5912F3TgsotxYYkKQLRsUp9grF3qejA%40mail.gmail.com.

Re: [vagrant-up] Access to Vagrant after migrating local user to Active directory user on a Mac

[Alvaro Miranda Aguilera]

Hello

If you are having your user to change and you want to keep the VMS then you
would have to do some manual work

base boxes are in ~/.vagrant.d
default VMs in Virtualbox are created in ~/VirtualBox VMs

as the path of the home user have have changed, your new user wont have
those directories

i would suggest to try to create new VMs using the project file / vagrant
up should create a new environment

If you need to copy things from the old VMs, you could login with
non-domain user, and extract the data / changes you need

Thanks!
Alvaro.

On Tue, Apr 7, 2020 at 7:52 PM Mark Kocour  wrote:

> How do I access Vagrant after migrating local user to Active directory
> user on a Mac.  How do I change the user name?
>
>
> --
> 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/f4390a70-29e7-4e9d-9037-a93f4aa72821%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/CAHqq0ewNJf4DtCFm%2BZNBPh9%2B1iU-jpDUnbP%2Ba56goXT2yQQToA%40mail.gmail.com.

Re: [vagrant-up] Confused

[Alvaro Miranda Aguilera]

Hello

The limitation is on VMWare side and not on vagrant.

Some VMWare player allows CLI/API calls to create VMS, has been reported
Linux VMWare player works
but the other doesn't

unfortunately is not a Vagrant limitation

Thanks
Alvaro


On Tue, Apr 7, 2020 at 5:29 PM El Presidente  wrote:

> Hi
>
> I am designing a system whose development environment is proposed to be
> based on custom Vagrant boxes with VMWare as a provider.
> Looking at the plugin requirements, it says I can use either the regular
> or Pro versions of Workstation or Fusion.
> Not seeing a non-Pro version of Workstation, I assumed that was
> Workstation Player (I've been out of the loop on VMWare for a bit). I got
> my company to pay for a couple of licences so we could prototype this.
> However, when I try to do 'vagrant up' I get:
>
> Vagrant encountered an error while attempting to inspect VMware
> for current version information:
>
>   The system cannot find the file specified.
>
> Looking at the FAQs on the Vagrant plugin site, I see it says some
> features may not work with VMWare Player and it isn't officially supported.
> But there's a big difference between 'not officially supported' and
> 'doesn't work at all'.
>
> So I'm trying to figure out if this is my problem (it literally does not
> work with Player and I need to speak nicely to VMWare and get them to
> refund the Player licences and sell us Workstation pro ones - and persuade
> my company to pay the additional cost), or if it's something else entirely.
> But I'm not getting anywhere.
>
> Has anyone any experience of this? Can you advise please?
> Cheers
>
> --
> 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/dd87c6b8-68a7-4330-916a-97dca5f972ea%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/CAHqq0ewv9yWOL8jeTF7JQRaGsumgL7622dEp6%2BerBJkCJc4hSw%40mail.gmail.com.

Re: [vagrant-up] Virtual Box bridged network and port forwarding VAGRANT

[Alvaro Miranda Aguilera]

it shoudl work without port forward

whats the output from the vm of

route -n
ip addr

as long default gw goes to the router it should work



On Fri, Apr 3, 2020 at 10:08 PM Yayaoui Namoussi  wrote:

> <https://i.gyazo.com/68dfcd78c251d7182009c766c7507def.png>
> This is my network :
>
> Le vendredi 3 avril 2020 21:14:31 UTC+2, Alvaro Miranda Aguilera a écrit :
>>
>> if you comment out and try from the home network, does work?
>>
>> do you have how to test ?
>>
>> you dont need port forward if the VM is having a public IP on the network
>>
>> On Fri, Apr 3, 2020 at 5:22 PM Yayaoui Namoussi 
>> wrote:
>>
>>> Hey guys i'm having serious problme with to portforward my port 5060 i'm
>>> stuck on it since 1 week :(
>>> the probleme is i want to portforward the port 5060 on my bridge network
>>> not in nat so naturaly i did this
>>>
>>>
>>>   config.vm.network "public_network", :bridge => "Realtek PCIe
>>> 2.5GbE Family Controller", :ip => "192.168.1.117"
>>>
>>>
>>> ###DEFAULT ROUTER##
>>> config.vm.provision "shell",
>>> run: "always",
>>> inline: "route add default gw 192.168.1.254"
>>>
>>>  config.vm.provision "shell",
>>> run: "always",
>>> inline: "eval `route -n | awk '{ if ($8 ==\"eth0\" && $2 !=
>>> \"0.0.0.0\") print \"route del default gw \" $2; }'`"
>>>   config.vm.network "forwarded_port", :adapter=>2, guest: 5060,host:
>>> 5060, protocol: "udp"
>>>
>>>
>>> Then when i do vagrant reload i have this
>>>
>>> default: VirtualBox adapter #2 not configured as "NAT".
>>> Skipping port
>>>
>>>
>>> in my router i did port forwarding like this 192.168.1.117 / UDP / ALL
>>> IP / 5060 / 5060
>>> and still when i try to check open port through internet its says the
>>> port is close
>>>
>>> --
>>> 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/d647b519-e8f0-4d38-a738-3398e4eb9e96%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/d647b519-e8f0-4d38-a738-3398e4eb9e96%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> 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/510b54bd-bf3f-487c-80bd-be9f9f42684e%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/510b54bd-bf3f-487c-80bd-be9f9f42684e%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
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/CAHqq0exLDe5N3xGtenSWUxSdMBmYgetT%3Dd9uYaHpiQQL92MNwQ%40mail.gmail.com.

Re: [vagrant-up] Unable to ssh into ubuntu/bionic64(error: The private key to connect to this box via SSH has invalid permissions)

[Alvaro Miranda Aguilera]

try if you can change the permission of the file

chmod 0600 /run/media/khg/149E4DD69E4DB0D2/uagrant/.vagrant/machines/
default/virtualbox/private_key
echo $?

if this doesnt work then you way want to use a different filesystem on this
guest



On Wed, Apr 1, 2020 at 4:10 PM Mohit Khulbe 
wrote:

> Hi,
> I am using manjaro Linux,
> the file system to the path is 'NTFS'
>
> thanks for asking,
>  what should I do now?
>
> On Wednesday, 1 April 2020 01:53:08 UTC+5:30, Alvaro Miranda Aguilera
> wrote:
>>
>> where are you running vagrant?
>>
>> whats the filesystem on this path /run/media/khg/149E4DD69E4DB0D2/uagrant
>>
>> whats your OS ?
>>
>> vagrant is failing to set the permissions of the private key to 0600
>>
>> of this file
>>
>>
>> /run/media/khg/149E4DD69E4DB0D2/uagrant/.vagrant/machines/default/virtualbox/private_key
>>
>> alvaro
>>
>> On Tue, Mar 31, 2020 at 7:35 PM Mohit Khulbe 
>> wrote:
>>
>>> Hi Vagrant community,
>>>
>>> I download the vagrant box ubuntu/bionic64
>>> <https://app.vagrantup.com/ubuntu/boxes/bionic64>
>>> when I run 'vagrant up' this error showed
>>>
>>>> The private key to connect to this box via SSH has invalid permissions
>>>>
>>>> set on it. The permissions of the private key should be set to 0600,
>>>>> otherwise SSH will
>>>>
>>>> ignore the key. Vagrant tried to do this automatically for you but
>>>>> failed. Please set the
>>>>
>>>> permissions on the following file to 0600 and then try running this
>>>>> command again:
>>>>
>>>>
>>>>>
>>>>> /run/media/khg/149E4DD69E4DB0D2/uagrant/.vagrant/machines/default/virtualbox/private_key
>>>>
>>>>
>>>>> Note that this error occurs after Vagrant automatically tries to
>>>>
>>>> do this for you. The likely cause of this error is a lack of filesystem
>>>>
>>>> permissions or even filesystem functionality. For example, if your
>>>>
>>>> Vagrant data is on a USB stick, a common case is that chmod is
>>>>
>>>> not supported. The key will need to be moved to a filesystem that
>>>>
>>>> supports chmod.
>>>>
>>>>
>>>>
>>> need suggestions, to work this issue
>>> thanks
>>>
>>>
>>> --
>>> 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/8b6c2a6d-2433-4734-955d-ecf70482846b%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/8b6c2a6d-2433-4734-955d-ecf70482846b%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> 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/5197f30d-5f48-4c17-b111-fc839416cc52%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/5197f30d-5f48-4c17-b111-fc839416cc52%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
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/CAHqq0eyCABbrhH3ahcrGm%2BSO7_WfWAvqA%2B75VHkuHLTmO4y_gw%40mail.gmail.com.

Re: [vagrant-up] Virtual Box bridged network and port forwarding VAGRANT

[Alvaro Miranda Aguilera]

if you comment out and try from the home network, does work?

do you have how to test ?

you dont need port forward if the VM is having a public IP on the network

On Fri, Apr 3, 2020 at 5:22 PM Yayaoui Namoussi  wrote:

> Hey guys i'm having serious problme with to portforward my port 5060 i'm
> stuck on it since 1 week :(
> the probleme is i want to portforward the port 5060 on my bridge network
> not in nat so naturaly i did this
>
>
>   config.vm.network "public_network", :bridge => "Realtek PCIe 2.5GbE
> Family Controller", :ip => "192.168.1.117"
>
>
> ###DEFAULT ROUTER##
> config.vm.provision "shell",
> run: "always",
> inline: "route add default gw 192.168.1.254"
>
>  config.vm.provision "shell",
> run: "always",
> inline: "eval `route -n | awk '{ if ($8 ==\"eth0\" && $2 !=
> \"0.0.0.0\") print \"route del default gw \" $2; }'`"
>   config.vm.network "forwarded_port", :adapter=>2, guest: 5060,host: 5060,
> protocol: "udp"
>
>
> Then when i do vagrant reload i have this
>
> default: VirtualBox adapter #2 not configured as "NAT". Skipping
> port
>
>
> in my router i did port forwarding like this 192.168.1.117 / UDP / ALL IP
> / 5060 / 5060
> and still when i try to check open port through internet its says the port
> is close
>
> --
> 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/d647b519-e8f0-4d38-a738-3398e4eb9e96%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/CAHqq0ezinUqM6WbTNOFkuRsy1xQq-rUmJXFk4R%3D51zF7mL%3DZog%40mail.gmail.com.

Re: [vagrant-up] Can Vagrantup w/ VirtualBox export a virual machine with its software to something that can run directly as a "main" OS?

[Alvaro Miranda Aguilera]

Hello

Not sure if you could do that, I know are tools to do the opposite.. Metal
-> VM

I don't think Vagrant can help, so you could try to see at disk level.

you could i assume boot on a liveCD and try to copy the virtual disk into
the real disk, however require some steps

ie convert the disk from vdi to raw/img



Alvaro.

On Wed, Apr 1, 2020 at 1:35 PM Nick The Wilde 
wrote:

> Can Vagrantup w/ VirtualBox export a virual machine with its software to
> something that can run directly as a "main" OS on another machine later?
>
> Basically, I want to prepare the software (Ubuntu with my desired
> applications) for a server on my main desktop and then create something
> like an ISO to be able to install/run directly on my server without the
> need of VirtualBox/VagrantUp
>
> And if so it would be nice if you could link me to some support page that
> describes the process/desired commands <3
>
> --
> 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/82418631-22a1-4f1b-9d7a-df6ae1ae29ef%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/CAHqq0ewjfKhdBihivB0QnusWyDaeh3NYxU%2BgboG2HiAxbLrSkA%40mail.gmail.com.

Re: [vagrant-up] Unable to use any vm box

[Alvaro Miranda Aguilera]

Hello

You can download the box file and add it with a local name

vagrant box add --name centos file.box

then you can update the Vagrantfile to use this name,  centos

in this way you will be sure its using the local box.

If you want to update the local box, then you can replace the file with

vagrant box add --force --name centos file.box


thanks
alvaro.

On Wed, Apr 1, 2020 at 11:16 AM Swarag Narayanasetty <
swaragcrash...@gmail.com> wrote:

> Hi,
>
> i tried installing a box for a online course and there was a box,
> https://app.vagrantup.com/jasonc/boxes/centos7
> since i from from india the download speed is limited to 1000/s when i use 
> vagrant
> box add jasonc/centos7 . The prompt says it would take about 30 hrs to
> complete download.
> so i downloaded the box manually from there and installed according the
> answer in stack overflow
>
> https://stackoverflow.com/questions/28399324/download-vagrant-box-file-locally-from-atlas-and-configuring-it
> so after i did that part
>
> when i start the box i would get this error:
>
> C:\Users\ACER AVENGER\shellclass\test01>vagrant up
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'jasonc/centos7'...
> ==> default: Matching MAC address for NAT networking...
> ==> default: Checking if box 'jasonc/centos7' version '1.4.4' is up to
> date...
> The box 'jasonc/centos7' is not a versioned box. The box was added
> directly instead of from a box catalog. Vagrant can only
> check the versions of boxes that were added from a catalog
> such as from the public Vagrant Server.
>
>
>
>
>
>
>
> *C:\Users\ACER AVENGER\shellclass\test01>vagrant box listjasonc/centos7
> (virtualbox, 1.4.4)*
>
> I tried updating the box but the same error keeps me from doing that,
>
> Any way solve this issue by not downloading the source once again through
>>
>>  vagrant box add jasonc/centos7
>>
>> by changing configuration file .
>>
>> thanks in advance.
>
>
> my issue is similar to
>
> https://laracasts.com/discuss/channels/laravel/version-error-after-homestead-box-direct-install
>
>
>
>
> --
> 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/40676dd2-b675-47a5-85fd-296b142016ad%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/CAHqq0ezyPUEbkiSXBGcjX86CWYNkWMOhsE5N97GzDh0VcfSnbw%40mail.gmail.com.

Re: [vagrant-up] Unable to ssh into ubuntu/bionic64(error: The private key to connect to this box via SSH has invalid permissions)

[Alvaro Miranda Aguilera]

where are you running vagrant?

whats the filesystem on this path /run/media/khg/149E4DD69E4DB0D2/uagrant

whats your OS ?

vagrant is failing to set the permissions of the private key to 0600

of this file

/run/media/khg/149E4DD69E4DB0D2/uagrant/.vagrant/machines/default/virtualbox/private_key

alvaro

On Tue, Mar 31, 2020 at 7:35 PM Mohit Khulbe 
wrote:

> Hi Vagrant community,
>
> I download the vagrant box ubuntu/bionic64
> 
> when I run 'vagrant up' this error showed
>
>> The private key to connect to this box via SSH has invalid permissions
>>
>> set on it. The permissions of the private key should be set to 0600,
>>> otherwise SSH will
>>
>> ignore the key. Vagrant tried to do this automatically for you but
>>> failed. Please set the
>>
>> permissions on the following file to 0600 and then try running this
>>> command again:
>>
>>
>>>
>>> /run/media/khg/149E4DD69E4DB0D2/uagrant/.vagrant/machines/default/virtualbox/private_key
>>
>>
>>> Note that this error occurs after Vagrant automatically tries to
>>
>> do this for you. The likely cause of this error is a lack of filesystem
>>
>> permissions or even filesystem functionality. For example, if your
>>
>> Vagrant data is on a USB stick, a common case is that chmod is
>>
>> not supported. The key will need to be moved to a filesystem that
>>
>> supports chmod.
>>
>>
>>
> need suggestions, to work this issue
> thanks
>
>
> --
> 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/8b6c2a6d-2433-4734-955d-ecf70482846b%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/CAHqq0ey55tU2qBuG7BgCocm_ChiG9v%2B%3DtsR853Bc5Xg_L3Gsgg%40mail.gmail.com.

Re: [vagrant-up] Question on port forwarding

[Alvaro Miranda Aguilera]

Hello
If you stop the VM from Virtualbox, and then start from VirtualBox GUI, you
wont be using vagrant at all

If you still have port issues, then could be how the ports get assigned
inside the VM.

I dont believe this is a Vagrant isuse as vagrant is running your scripts
after creating the VM

Alvaro


On Wed, Mar 25, 2020 at 10:38 PM Sorcerer Stone 
wrote:

> Hello Alvaro,
> Indeed I have. But I am running into problems and I am guessing port
> conflicts is the cause. But it could be others such as port forwarding.
> Hence my question.
> I have 2 separate projects which has its own Postgres, and one has its own
> Nginx.
> On their own, I can use Vagrant file to call up the Compose yml file and
> containers all running in each of these project and I can access the app
> through the browser.
> But when I put the 2 separate projects into one big compose file and make
> sure the ports used in Postgres are different for each of these apps
> services. Containers are running but the app got errors like "Network not
> found" or something like that when I tried to access them.
> So, I am looking into could the problem be in port forwarding. But it make
> no sense to forward internal ports onto the host OS.
> I will keep hacking. Thanks for the confirmation about no need to forward
> ports used internally among containers in the guest OS.
> SStone.
>
> On Wednesday, March 25, 2020 at 4:10:56 PM UTC-4, Alvaro Miranda Aguilera
> wrote:
>>
>> Hello
>>
>> The answer to your question I believe is a yes as you mention, as you say
>> you want internal services.
>>
>> have you tested ?
>>
>>
>>
>> On Wed, Mar 25, 2020 at 8:48 PM Sorcerer Stone 
>> wrote:
>>
>>> Vagrantup.com described the general guideline of port forwarding usage.
>>> I have a question which I think the answer is most likely No. But need
>>> confirmation from others as I am self-learning.
>>>
>>> In a docker compose file, say defining the db service for setting up
>>> postgres, there are ports statement like
>>>
>>> ports:
>>>   - "5432:5432"
>>>
>>> Am I correct to say internal ports like this that are need to
>>> communicate with other services/running containers (that are placed on the
>>> same network) do not need port forwarding to be define in the vagrantfile
>>> (aka, in this example, port 5432 need not be forwarded as host OS does not
>>> use it)?
>>>
>>> Correct?
>>>
>>> Thanks in advance.
>>> SStone
>>>
>>> --
>>> 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/f5a62767-21fb-44ca-90d2-890f9b07b1f9%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/f5a62767-21fb-44ca-90d2-890f9b07b1f9%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> 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/c4e75b6a-f59a-489b-babd-aef54b447041%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/c4e75b6a-f59a-489b-babd-aef54b447041%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
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/CAHqq0ew_293rQzkjexBZEa-eAzhRLZ%3DbvGnJOfC8bNNiY1SdAA%40mail.gmail.com.

Re: [vagrant-up] Question on port forwarding

[Alvaro Miranda Aguilera]

Hello

The answer to your question I believe is a yes as you mention, as you say
you want internal services.

have you tested ?



On Wed, Mar 25, 2020 at 8:48 PM Sorcerer Stone 
wrote:

> Vagrantup.com described the general guideline of port forwarding usage.
> I have a question which I think the answer is most likely No. But need
> confirmation from others as I am self-learning.
>
> In a docker compose file, say defining the db service for setting up
> postgres, there are ports statement like
>
> ports:
>   - "5432:5432"
>
> Am I correct to say internal ports like this that are need to communicate
> with other services/running containers (that are placed on the same
> network) do not need port forwarding to be define in the vagrantfile (aka,
> in this example, port 5432 need not be forwarded as host OS does not use
> it)?
>
> Correct?
>
> Thanks in advance.
> SStone
>
> --
> 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/f5a62767-21fb-44ca-90d2-890f9b07b1f9%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/CAHqq0eyWdssTXjwk6COpg-79r%3DG6PFVyFHiOr9QGDW88tVo2_Q%40mail.gmail.com.

Re: [vagrant-up] How to install vagrant-vbguest plugin without Internet?

[Alvaro Miranda Aguilera]

hello

to answer your question.
you could download the gem file and then try
vagrant plugin install 

however the only thing this plugin does is to reinstall virtualbox guest
additions if not detected, the operation on the vm may need internet, as
the OS may need packages (perl gcc kernel-headers kernel-sources)

so i think will be better if you create your own box ready to use, and then
on the machines without internet access you just use them

this will also make happier the end user as will be quicker

you can use packer tool to build boxes, and you can use bento boxes as
sample starting points

https://packer.io/downloads.html

https://github.com/chef/bento

alvaro

On Tue, Mar 17, 2020 at 3:35 PM Siew  wrote:

> Hi Vagrant community
>
> I installed vagrant-vbguest plugin successfully in a virtual box that is
> connected to Internet using "vagrant plugin install vagrant-vbguest".
>
> I had to reproduce the above in my offline production environment and
> without internet, it did not work.
> Error was "Vagrant failed to load a configured plugin source... no such
> name (https://gems.hashicorp.com/specs.4.8.gz)".
>
> How can I install VirtualBox guest additions offline?
>
> Many thanks in advance.
>
>
> This email is intended only for the named addressee(s) and may contain
> confidential and/or privileged information. If you are not the named
> addressee (or have received this e-mail in error), please notify the sender
> immediately. The unauthorised use, disclosure, distribution or copying of
> the contents in this e-mail is prohibited.
>
> 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/5d21bfd5-0533-4fad-8e71-a70b9cbb7908%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/CAHqq0ewJTfO6rXDSev2nnrM9WZW%3DRGPEFRwgcbZ7vntKX8sEZQ%40mail.gmail.com.

Re: [vagrant-up] Having troubles trying to make a Hyper-V box

[Alvaro Miranda Aguilera]

hello

i think the file need to be tar

you can try to inspect an existing hyper-v vm and test repackage it

here is one example:

https://vagrantcloud.com/hashicorp/boxes/bionic64/versions/1.0.282/providers/hyperv.box




kikitux@nuc8:~/Downloads$ mkdir h


kikitux@nuc8:~/Downloads$ cd h

kikitux@nuc8:~/Downloads/h$ tar zxvf ../hyperv.box


metadata file is quite simple







cat metadata.json

{"provider":"hyperv"}


alvaro


On Fri, Mar 20, 2020 at 1:10 AM Ariel JGS  wrote:

> Hello, I've been trying to make a new Hyper-V box but I don't know what am
> I doing wrong, I'm following the steps in the documentation and I'm not
> sure where is the mistake. I made a debian VM with Hyper-V, it has 1 GB
> RAM, 100GB hard disk, user vagrant with password vagrant, same with root, I
> installed the hyperv-daemons so the VM reports its IP address in the
> "networking" tab. I exported my VM and it generated 3 folders: Snapshots,
> Virtual Hard Disks and Virtual Machines. I deleted Snapshots and created a
> metadata.json file with the following information:
>
> {
>   "name": "arieljgs/debian10",
>   "description": "This box contains Debian 10.03 CLI 64-bit.",
>   "versions": [
> {
>   "version": "1.0",
>   "providers": [
> {
>   "name": "hyperv",
> }
>   ]
> }
>   ]}
>
>
> Then I added everything to a .zip file, including the .json file. After
> that I used the command vagrant box add --name arieljgs/debian10
> "D:\Vagrant Boxes\Debian 10.3.0 CLI\Debian 10.3.0 CLI.zip" and I'm getting
> the following error:
>
> The metadata associated with the box 'arieljgs/debian10' appears corrupted.
> This is most often caused by a disk issue or system crash. Please
> remove the box, re-add it, and try again.
>
> Does anyone know what's happening here? Any help will be appreciated
>
> --
> 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/671e0ac5-7e87-40cc-98a6-ac5be6abf435%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/CAHqq0ew90-RFYB%3Dw29U6kEGUSRDvMesxn2Ryd50CjtKJqw1rYw%40mail.gmail.com.

Re: [vagrant-up] now vagrant up in Homestead Not booting...

[Alvaro Miranda Aguilera]

hello

i would suggest open virtualbox

stop the VM
start the VM

see if there is any error

also

try to create and boot a VM directly on virtualbox

alvaro

On Fri, Mar 20, 2020 at 11:15 AM LSE  wrote:

> yesterday was working
> now vagrant up in Homestead Not booting... I just now upgraded Virtual Box
> to VirtualBox-6.1.4-136177-Win.exe but the same result... what to do?
>
> zzz@yyyMINGW64 /f/htdocs_xampp/Laravel/Homestead2020 (master)
> *$ vagrant up*
> Bringing machine 'homestead' up with 'virtualbox' provider...
> ==> homestead: Checking if box 'laravel/homestead' version '9.3.0' is up
> to date...
> ==> homestead: Resuming suspended VM...
> ==> homestead: Booting VM...
> ==> homestead: Waiting for machine to boot. This may take a few minutes...
> homestead: SSH address: 127.0.0.1:
> homestead: SSH username: vagrant
> homestead: SSH auth method: private key
> Timed out while waiting for the machine to boot. This means that
> Vagrant was unable to communicate with the guest machine within
> the configured ("config.vm.boot_timeout" value) time period.
>
> If you look above, you should be able to see the error(s) that
> Vagrant had when attempting to connect to the machine. These errors
> are usually good hints as to what may be wrong.
>
> If you're using a custom box, make sure that networking is properly
> working and you're able to connect to the machine. It is a common
> problem that networking isn't setup properly in these boxes.
> Verify that authentication configurations are also setup properly,
> as well.
>
> If the box appears to be booting properly, you may want to increase
> the timeout ("config.vm.boot_timeout") value.
>
> zzz@yyyMINGW64 /f/htdocs_xampp/Laravel/Homestead2020 (master)
>
> --
> 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/f2a38503-dc4c-4bc7-9637-552aab709a92%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/CAHqq0ew5OvMo7WOWNDM-qd1M%2B_Kpe%3D338zVn6T027%2B-HOxKaSQ%40mail.gmail.com.

Re: [vagrant-up] nextcloud vagrant

[Alvaro Miranda Aguilera]

in the old days, some services had bind options and also allow/deny
parameters

you could check for each of those services if you can telnet the port
and check documentation for each of those, could be /etc/hosts.allow
/etc/hosts.deny or the same service having an allow/deny setting

On Fri, Mar 20, 2020 at 11:15 PM torches  wrote:

>
> I setup a nextcloud via vagrant and I am able to reach ports 22,80,443 via
> the bridged ip from outside the guest but not 389 (ldap) as well as other
> ports. selinux is disabled, as well as the firewall. Anyone knows the
> reason for this behavior?
>
> [vagrant@nc ~]$ netstat -na | grep -w 389
> tcp0  0 0.0.0.0:389 0.0.0.0:*
> LISTEN
> tcp6   0  0 :::389  :::*
> LISTEN
>
>
> my Vagrantfile:
> nc.vm.box = "ale_polidori/Nextcloud"
> nc.vm.network "public_network", ip: "192.168.86.68"
> nc.vm.hostname = "nc"
>
> --
> 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/002bdf57-2c78-4c68-a4f7-d7da198e0792%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/CAHqq0eyR6tC687D4C3cvxRPt8SrAuGMZ52ZgX8N4QqfOQpDzaA%40mail.gmail.com.

Re: [vagrant-up] Can (and how) additional OS rpms be added to generic/centos7 or generic/rhel7 Vagrant boxes ?

[Alvaro Miranda Aguilera]

hello

in general:

you can run scripts and install the software you need.
https://www.vagrantup.com/docs/provisioning/shell.html

if the process is too slow, you can build your own boxes ready to use.

Alvaro

On Sat, Mar 14, 2020 at 9:39 PM BDutta  wrote:

> Hi,
>
> Absolute Vagrant newbie here.
>
> Are the generic/centos7 or generic/rhel7 Vagrant boxes, extensible or
> upgradable such that additional operating system rpms could be installed ?
> I am assuming that those boxes might be setup using the minimal image?
> What if I need some of the rpms that are available as part of standard
> RHEL7/CentOS7 distribution, but not on the box ?
>
> cheers,
> B
>
> --
> 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/6fd3fac4-75e0-4c20-b064-a1d053ee439d%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/CAHqq0eymBaMOLrjD2AfKXUdpe%2B8mzKApZ4XYdEEzkUKj%2B%2BtJLQ%40mail.gmail.com.

Re: [vagrant-up] Do I need port-forwarding to communicate from host to guest?

[Alvaro Miranda Aguilera]

Hello

On a technical side both are similar.

However in Linux/MacOS, only root or elevated process can open port under
1024

So people usually do port forwarding like 8080 -> VM:80

using the private ip:80 feels more like working with your own server over
the network

of course there is nothing bad using one or the other, as both do the same.

on same high traffic task, sometimes port forward / nat can be slower than
hitting private_ip:80

Alvaro.

On Mon, Mar 9, 2020 at 10:27 AM zveratko  wrote:

> I am asking because I am not sure how those public/bridged etc. networking
> between host/guest works. Sometime I cannot see the port on the host. Maybe
> it is because the app in the VM is restricted to accept localhost
> connection only, but I always strugling to find the exact place of the
> error.
>
> Are those option equal ?
> call 192.168.10.101:80 on host machine
> make port-forward 80:80 and call localhost:80 on host machine
>
> Is the first option using NAT while the second is not?
>
>
> On Saturday, March 7, 2020 at 12:59:34 PM UTC+1, Alvaro Miranda Aguilera
> wrote:
>>
>> hello
>>
>> if you want to access something on port 80 then you can use 192.168.
>> 10.101:80
>>
>> http://192.168.10.101
>>
>>
>> On Fri, Mar 6, 2020 at 12:17 PM zveratko  wrote:
>>
>>> I have set up some vagrant box and I want to connect to some services
>>> running on it. I used this to set up the networking
>>>
>>>  config.vm.network "private_network", ip: "192.168.10.101"
>>>
>>>
>>> I checked in VirtualBoxUI and the machine has two interfaces NAT with
>>> port forwarding ->22(probably the eth0) and HOST_ONLY(eth1?)
>>>
>>> eth0: flags=4163  mtu 1500
>>> inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
>>> inet6 fe80::a00:27ff:fec2:4a97  prefixlen 64  scopeid 0x20
>>> ether 08:00:27:c2:4a:97  txqueuelen 1000  (Ethernet)
>>> RX packets 27643  bytes 24238095 (23.1 MiB)
>>> RX errors 0  dropped 0  overruns 0  frame 0
>>> TX packets 11304  bytes 1136140 (1.0 MiB)
>>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>>
>>>
>>> eth1: flags=4163  mtu 1500
>>> inet 192.168.10.101  netmask 255.255.255.0  broadcast 192.168.
>>> 10.255
>>> inet6 fe80::a00:27ff:fe19:fc5  prefixlen 64  scopeid 0x20
>>> ether 08:00:27:19:0f:c5  txqueuelen 1000  (Ethernet)
>>> RX packets 3053  bytes 278689 (272.1 KiB)
>>> RX errors 0  dropped 0  overruns 0  frame 0
>>> TX packets 2380  bytes 683097 (667.0 KiB)
>>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>>
>>>
>>> Do I need port forwarding to access some service running inside on port
>>> ie.80? I have just tested that I can putty in by localhost: or
>>> 192.168.10.101:22
>>>
>>> In which setting I can ommit port forwarding and just call guest with
>>> its ip? I have some problems connecting to another service and I am not
>>> sure whather it just listen to localhost only or something else is wrong.
>>>
>>> Is this sentence I noted some time ago correct
>>>
>>> port forwarding is not needed when using private network and accessing
>>> guest from host with guest private ip, port forwarding is used to access
>>> guest with localhost/127.0.0.1 the ports are then forwarded
>>>
>>> --
>>> 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/63a27481-91a3-42b4-a93a-4aa7c49a424f%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/63a27481-91a3-42b4-a93a-4aa7c49a424f%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> Alvaro
>>
>> --
> This mailing list is governed under the HashiCorp Commu

Re: [vagrant-up] How to change the default networking

[Alvaro Miranda Aguilera]

If the process you are doing is just automatic, ie runnign scripts, the
best would be use packer.

packer have builders.
vmware-iso that can start from an iso and create a VM
but also have vmware-vmx that can start from an existing vm. this one is
good to create specific VMS from a base template.

For your question,
You can try something like this:


 config.vm.network "public_network", adapter: 0, auto_config: false


But I am not sure the right syntax if you want multiple networks.



alvaro

On Thu, Mar 5, 2020 at 10:11 PM Adrian Wallaschek 
wrote:

> Hi! I use Vagrant to build and configure VMs that later I want to deploy
> to vSpere. rsp. vCloud Director.
>
> The structure is simple: there will be proxies and a jumpserver, each with
> one NIC in a DHCP-configured public network. They all will have a second
> NIC in a private network that uses fixed IP addresses.
>
> Now when I build these machines, each ends up with three NICs: one for
> Vagrant, one for the private (as configured) and one for the public (as
> configured). While the configured NICs work, the Vagrant-NIC is disturbing
> me.
>
> Yes, I can make an Ansible-Playbook to disable this one or a PowerCLI
> script to kill the NIC upon instantiation of the VM from the
> Content-Library.
>
>
> What I would love, though, ist to re-configure the Vagrant internal
> networking to happen on that private interface. Is that possible? Can I
> redefine the network that Vagrant uses for configuring the machine?
>
> Best ragards and thx in advance!
>
> --
> 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/7655e701-4d38-430a-a353-b0ffb618b888%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/CAHqq0ezT4fCcAh--3cCmHE6X6zdFUumAXg9O-dR8PGLxA2WsgA%40mail.gmail.com.

Re: [vagrant-up] Do I need port-forwarding to communicate from host to guest?

[Alvaro Miranda Aguilera]

hello

if you want to access something on port 80 then you can use 192.168.
10.101:80

http://192.168.10.101


On Fri, Mar 6, 2020 at 12:17 PM zveratko  wrote:

> I have set up some vagrant box and I want to connect to some services
> running on it. I used this to set up the networking
>
>  config.vm.network "private_network", ip: "192.168.10.101"
>
>
> I checked in VirtualBoxUI and the machine has two interfaces NAT with port
> forwarding ->22(probably the eth0) and HOST_ONLY(eth1?)
>
> eth0: flags=4163  mtu 1500
> inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
> inet6 fe80::a00:27ff:fec2:4a97  prefixlen 64  scopeid 0x20
> ether 08:00:27:c2:4a:97  txqueuelen 1000  (Ethernet)
> RX packets 27643  bytes 24238095 (23.1 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 11304  bytes 1136140 (1.0 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
> eth1: flags=4163  mtu 1500
> inet 192.168.10.101  netmask 255.255.255.0  broadcast 192.168.
> 10.255
> inet6 fe80::a00:27ff:fe19:fc5  prefixlen 64  scopeid 0x20
> ether 08:00:27:19:0f:c5  txqueuelen 1000  (Ethernet)
> RX packets 3053  bytes 278689 (272.1 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 2380  bytes 683097 (667.0 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
> Do I need port forwarding to access some service running inside on port
> ie.80? I have just tested that I can putty in by localhost: or
> 192.168.10.101:22
>
> In which setting I can ommit port forwarding and just call guest with its
> ip? I have some problems connecting to another service and I am not sure
> whather it just listen to localhost only or something else is wrong.
>
> Is this sentence I noted some time ago correct
>
> port forwarding is not needed when using private network and accessing
> guest from host with guest private ip, port forwarding is used to access
> guest with localhost/127.0.0.1 the ports are then forwarded
>
> --
> 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/63a27481-91a3-42b4-a93a-4aa7c49a424f%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/CAHqq0ez5Cv9iPn0bvznz_%2B5dkMNEx6nB31Gec%3Ds4q%3DWyAidXvQ%40mail.gmail.com.

Re: [vagrant-up] vagrant box build using VirtualBox - oracle linux 7 internal network cannot communicate with other internal network outside of the vagrant boxes built

[Alvaro Miranda Aguilera]

hello

vagrant by default will create the new VMS NAT only, so the VMs have access
to your host and from there what your host can reach,

if you have multiple vms, the IP is nat only so it shoulnt allow you
contact between them.

If you have VMS managed out of vagrant, you should be able to access them
if you are using any networking other than NAT,

alvaro

On Sat, Feb 29, 2020 at 6:25 PM K  wrote:

> I did write a summary but it got longer and longer.
> So, I will try to be direct, even if it sounds stupid.
>
> I'm new to Vagrant.
> After a Vagrant Linux box is built and up and running inside VirtualBox,
> does Vagrant have any kind of, lets say, 'firewall' around the boxes
> network that makes the VMs from Vagrant different from the VMs built
> straight in VirtualBox by hand ?
> Or , once created in VirtualBox - they are independent in the way they run
> ( ie have left the Vagrant 'system of operation' behind ) with regards
> networking.
>
> Im really getting desperate to ask such an apparently idiotic question
> believe me.
> I don't want to drag people into a network discussion. Im just trying to
> binary chop the issue so I can see whether I can ignore Vagrant at this
> stage.
> .
>
>
>
>
> --
> 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/21251489-1d9e-4b3d-a6ab-793d959b5d3a%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/CAHqq0ezd5EUuGF%2BgfLuHJ-PZyiz89fAnpbu0uAk7a8bd%2BZ9c3g%40mail.gmail.com.

Re: [vagrant-up] vagrant up failing to upgrade guest vbox version

[Alvaro Miranda Aguilera]

you can try the vbguest plugin

vagrant plugin install vagrant-vbguest

then vagrant reload
or vagrant up


On Tue, Mar 3, 2020 at 5:01 PM Donald Raikes  wrote:

> Thanks for the suggestions, but because I am using a lot of the
> vagrant boxes from Oracle's repository, I need to stick with their
> default boxes.
>
> I can try to do the install manually, but I am not certain howwhat
> packages to install or uninstall :)
>
> On 3/2/20, Alvaro Miranda Aguilera  wrote:
> > hello
> >
> > seems the box you are using is not having virualbox guest additions
> > installed.
> >
> > you could try to install them and see if works, or build your own box
> ready
> > to use.
> >
> >
> > On Sun, Mar 1, 2020 at 11:34 PM Donald Raikes 
> wrote:
> >
> >> Hello,
> >>
> >> I just upgraded both virtualbox and vagrant on my windows 10 system.
> >>
> >> Virtualbox is not version 6.1.4
> >> vagrant is 2.2.7
> >>
> >> when I use vagrant up on an oraclelinux 7 box, it says the host
> >> edition isand guest vbox editions are mismatched, and it is unable to
> >> mount the shared folders.
> >>
> >> This used to work on my older configuration so is it just something to
> >> do with the newer vagrant or virtual box?
> >>
> >> the error message I am getting is:
> >> Mounting shared folders...
> >> ol7-vagrant: /vagrant => V:/7
> >>
> >>   Vagrant was unable to mount VirtualBox shared folders. This
> >> is usually  because
> >> the filesystem "vboxsf" is not available. This filesystem is
> >>  made available via the
> >> VirtualBox Guest Additions and kernel module.
> >>   Please verify that these guest additions are
> >> properly installed in the
> >> guest. This is not a bug in Vagrant and is usually caused by a
> >> faulty   Vagrant box.
> >> For context, the command attempted was:
> >>
> >>
> >>   mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
> >>
> >>
> >>  The error output from the
> >> command was:
> >>
> >>
> >>  /sbin/mount.vboxsf: mounting failed with the error: No such device
> >>
> >> Any help would be greatly appreciated.
> >>
> >> Thanks,
> >> Donald
> >>
> >> --
> >> 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/CAPamLv9FNJp2vGf_trMW_8OGKbd37cp7qTDe-m9T1OkYJpOHpQ%40mail.gmail.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/CAHqq0exoUa_oExBb0fuO7wUmmXVFmz399zK%2B2Dc_3XU6A8AASQ%40mail.gmail.com
> .
> >
>
> --
> 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.
>
> Git

Re: [vagrant-up] vagrant up failing to upgrade guest vbox version

[Alvaro Miranda Aguilera]

hello

seems the box you are using is not having virualbox guest additions
installed.

you could try to install them and see if works, or build your own box ready
to use.


On Sun, Mar 1, 2020 at 11:34 PM Donald Raikes  wrote:

> Hello,
>
> I just upgraded both virtualbox and vagrant on my windows 10 system.
>
> Virtualbox is not version 6.1.4
> vagrant is 2.2.7
>
> when I use vagrant up on an oraclelinux 7 box, it says the host
> edition isand guest vbox editions are mismatched, and it is unable to
> mount the shared folders.
>
> This used to work on my older configuration so is it just something to
> do with the newer vagrant or virtual box?
>
> the error message I am getting is:
> Mounting shared folders...
> ol7-vagrant: /vagrant => V:/7
>
>   Vagrant was unable to mount VirtualBox shared folders. This
> is usually  because
> the filesystem "vboxsf" is not available. This filesystem is
>  made available via the
> VirtualBox Guest Additions and kernel module.
>   Please verify that these guest additions are
> properly installed in the
> guest. This is not a bug in Vagrant and is usually caused by a
> faulty   Vagrant box.
> For context, the command attempted was:
>
>
>   mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
>
>
>  The error output from the
> command was:
>
>
>  /sbin/mount.vboxsf: mounting failed with the error: No such device
>
> Any help would be greatly appreciated.
>
> Thanks,
> Donald
>
> --
> 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/CAPamLv9FNJp2vGf_trMW_8OGKbd37cp7qTDe-m9T1OkYJpOHpQ%40mail.gmail.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/CAHqq0exoUa_oExBb0fuO7wUmmXVFmz399zK%2B2Dc_3XU6A8AASQ%40mail.gmail.com.

Re: [vagrant-up] package failing

[Alvaro Miranda Aguilera]

Hello

Error is telling you in the tmp directory there is already a directory/file
with the same name

cleanup .vagrant.d/tmp and try again please

alvaro

On Tue, Feb 25, 2020 at 10:15 AM 'Thomas Carney' via Vagrant <
vagrant-up@googlegroups.com> wrote:

> HI,
>
>
> I am having difficulty packaging an existing VM into a vagrant box.
>
>
> When I type the package command and press return, the program seems to do
> something. I get the line "==> [VMName]: Exporting VM" and it hangs for
> about 20 minutes. Then it fails, always with the same error as shown below.
>
>
>
> [image: vagrant package failure.png]
>
> Can anyone give me any clue as to what is happening here?
>
> Thanks
>
> --
> 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/201a3513-fb70-47d3-97d8-b641bccebb3a%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/CAHqq0exj2488BSys-k%2BEX4RwoJSj7ean4DyBL4YKzrpA9WE3xQ%40mail.gmail.com.

Re: [vagrant-up] vagrant 2.2.7 and error with RHEL 8...

[Alvaro Miranda Aguilera]

Hello

Can you share the Vagrantfile you are using in your project and also the
Vagrantfile included in the box?


/Users/gmarti1/.vagrant.d/boxes/rhel8/0/virtualbox/Vagrantfile

Thanks
Alvaro.

On Tue, Feb 25, 2020 at 1:06 PM Gael Martinez 
wrote:

> I'm encountering this error using a rhel 8 box that used to work in the
> past with older versions of vagrant... If extracting the .box file and
> using directly the VBox configuration and loading it into VBox it works
> just fine...
>
> The same issue happens on MacOS Mojave, vagrant 2.2.7, Virtualbox 6.0.12,
> 6.0.18, 6.1.2 and 6.1.4... The following error seems to repeat  in loop for
> a few minutes until a final crash...
>
>  INFO global: Vagrant version: 2.2.7
>  INFO global: Ruby version: 2.4.9
>  INFO global: RubyGems version: 2.6.14.4
>  INFO global: VAGRANT_DEFAULT_PROVIDER="virtualbox"
>  INFO global: VAGRANT_INSTALLER_VERSION="2"
>  INFO global: VAGRANT_INSTALLER_ENV="1"
>  INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
>  INFO global:
> VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/bin/vagrant"
>  INFO global: VAGRANT_LOG="debug"
>  WARN global: resolv replacement has not been enabled!
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/synced_folders/nfs/plugin.rb
>  INFO manager: Registered plugin: NFS synced folders
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/synced_folders/rsync/plugin.rb
>  INFO manager: Registered plugin: RSync synced folders
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/synced_folders/smb/plugin.rb
>  INFO manager: Registered plugin: SMB synced folders
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/kernel_v2/plugin.rb
>  INFO manager: Registered plugin: kernel
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/pushes/ftp/plugin.rb
>  INFO manager: Registered plugin: ftp
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/pushes/noop/plugin.rb
>  INFO manager: Registered plugin: noop
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/pushes/heroku/plugin.rb
>  INFO manager: Registered plugin: heroku
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/pushes/local-exec/plugin.rb
>  INFO manager: Registered plugin: local-exec
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/pushes/atlas/plugin.rb
>  INFO manager: Registered plugin: atlas
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/docker/plugin.rb
>  INFO manager: Registered plugin: docker-provider
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/hyperv/plugin.rb
>  INFO manager: Registered plugin: Hyper-V provider
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/plugin.rb
>  INFO manager: Registered plugin: VirtualBox provider
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/kernel_v1/plugin.rb
>  INFO manager: Registered plugin: kernel
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/provisioners/docker/plugin.rb
>  INFO manager: Registered plugin: docker
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/provisioners/file/plugin.rb
>  INFO manager: Registered plugin: file
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/provisioners/shell/plugin.rb
>  INFO manager: Registered plugin: shell
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/provisioners/chef/plugin.rb
>  INFO manager: Registered plugin: chef
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/provisioners/ansible/plugin.rb
>  INFO manager: Registered plugin: ansible
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/provisioners/salt/plugin.rb
>  INFO manager: Registered plugin: salt
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/provisioners/cfengine/plugin.rb
>  INFO manager: Registered plugin: CFEngine Provisioner
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/provisioners/puppet/plugin.rb
>  INFO manager: Registered plugin: puppet
> DEBUG global: Loading core plugin:
> /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/commands/provision/plugin.rb
>  INFO manager: Registered 

Re: [vagrant-up] How to show real ip client in flask on vagrant VM

[Alvaro Miranda Aguilera]

if you add a private network or a public network, then use that ip to
access the webserver, it should show the ip of the guest

On Sat, Feb 15, 2020 at 7:46 AM Javad Rajabzade  wrote:

> 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
> 
> .
>


-- 
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/CAHqq0ewpe0FuU_kRD7VRaO6K9bQu_dKuzXHN7Q87EWj9Gr-1sA%40mail.gmail.com.

Re: [vagrant-up] vagrant up error

[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] Re: Install vagrant from source files on a local setup without internet

[Alvaro Miranda Aguilera]

hello

vagrant is a good tool to create development environments

using a plugin method it have a host / provide / guest model

installing vagrant on a ARM host, is not today part of the installers, so i
would ask first

are there any tool out of the box that can help you to do whatever you want
to do ?

otherwise you may invest time into making vagrant work on ARM but maybe
other tooling can do the work for you

i can think on try docker or LXC containers

How much ram your ARM machine have?

-- 
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/CAHqq0exVGV7me5yxdJL3cF7%3DfSoqnua6863q%3D4%2B9fTj6rvWCEg%40mail.gmail.com.

Re: [vagrant-up] Installing Vagrant 2.2.7 doesn't do anything.

[Alvaro Miranda Aguilera]

hello

what the host os ?

if linux or macos check the binary path, you can use which vagrant and see
the path of the binary

try to remove the old version before installing the new one would be a good
first step

alvaro



On Mon, Feb 10, 2020 at 4:36 PM iiRobin  wrote:

> Hello all,
>
> I tried to upgrade from vagrant 2.1.4 to the latest version which is
> 2.2.7. I downloaded the installer and everything seemed to be working. When
> it was done installing I restarted my PC and checked the version of Vagrant
> in my console, and it still said 2.1.4... I tried again, but still the same
> result. Can anyone help me with this since I really need this to work :)
>
> Thanks for your help in advance
>
> - Robin
>
>
> --
> 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/eca47b89-ca6d-40b8-a176-5623ca28aabf%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/CAHqq0ewuLd9xfPPvPfd5ELGJxC4q5%3DS-auW98E-BVmCkP7wZag%40mail.gmail.com.

Re: [vagrant-up] Ansible introductory page not available in documentation menu

[Alvaro Miranda Aguilera]

Hello!

Thanks for sharing this

Vagrant development team will be fixing this soon.

Thanks again
alvaro

On Mon, Jan 20, 2020 at 12:10 PM 林博仁  wrote:

> Hello, I would like to inform you that the Ansible - Short Introduction -
> Vagrant by HashiCorp
>  page
> isn't available in the left side menu, which prevents readers for accessing
> introductory materials.
>
> --
> 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/5c7ef78f-a582-4886-8c5f-c0c73e434a40%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/CAHqq0eyw8-Evz566E9rq0z3tJVuJS25qTDw_YULmLhuhBoNQ%3DQ%40mail.gmail.com.

Re: [vagrant-up] Debian Buster boxes, virtualbox, and guest plugins

[Alvaro Miranda Aguilera]

best will be build a box fit to your own use

you can use
https://www.packer.io/

you can find templates here:
https://github.com/chef/bento

alvaro


On Mon, Jan 27, 2020 at 1:14 AM Matthew Pounsett  wrote:

>
> I'm using VirtualBox 6.0.14, Vagrant 2.2.6 with the vagrant-vbguest 0.23.0
> plugin.  I'm trying to get a Debian Buster box working, but I'm having huge
> problems with the guest plugins.
>
> Using the 'debian/buster64' box, the guest plugin install fails because
> the box is out of date compared to the buster packages actually available
> online (10.0.0 vs. 10.2)
>
> E: Unable to locate package linux-headers-4.19.0-5-amd64
> E: Couldn't find any package by glob 'linux-headers-4.19.0-5-amd64'
> E: Couldn't find any package by regex 'linux-headers-4.19.0-5-amd64'
>
> Using the 'generic/debian10' box, I run into a problem where the box
> already has the VirtualBox 5.1.38 guest additions installed, and
> vagrant-vbguest appears to succeed in updating them, but the default
> /vagrant shared folder fails to mount.  A couple of potential errors pop up
> during the upgrade:
>
> Removing installed version 5.1.38 of VirtualBox Guest Additions...
> ./install.sh: 143: ./install.sh: VBoxControl: not found
> This system appears to have a version of the VirtualBox Guest Additions
> already installed.  If it is part of the operating system and kept
> up-to-date,
> there is most likely no need to replace it.  If it is not up-to-date, you
> should get a notification when you start the system.  If you wish to
> replace
> it with this version, please do not continue with this installation now,
> but
> instead remove the current version first, following the instructions for
> the
> operating system.
>
> If your system simply has the remains of a version of the Additions you
> could
> not remove you should probably continue now, and these will be removed
> during
> installation.
>
> Do you wish to continue? [yes or no]
> touch: cannot touch '/var/lib/VBoxGuestAdditions/skip-4.19.0-6-amd64': No
> such file or directory
> Copying additional installer modules ...
>
>
> And later in my provisioning script:
>
> vm01: ls: cannot access '/vagrant': No such file or directory
>
>
> If I halt and restart the VMs, they appear to boot with the correct
> GuestAdditions, but I still don't get the /vagrant shared folder.
>
> [vm01] GuestAdditions 6.0.14 running --- OK.
>
>
>  I'm not sure what to poke at here to fix this.
>
> --
> 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/4576d093-6e15-4c9a-974d-862cb9c0c8b7%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/CAHqq0exmTDru0-Ugc73OhD8kpaWif%3D5tYNkDPpJYqOqGy5xC2g%40mail.gmail.com.

Re: [vagrant-up] Vagrant encountered an error while attempting to load the utility service key file - No such file or directory

[Alvaro Miranda Aguilera]

Hello

Vagrant vmware plugin support is done by email to support @ hashicorp.com

basically reinstall the utility:
 https://www.vagrantup.com/docs/vmware/vagrant-vmware-utility.html

are you login by this admin user and you running the commands under this
user?

if you have issues, email support and we will assist you there

thanks
alvaro.

On Thu, Jan 2, 2020 at 12:23 AM craig bowser  wrote:

>
> I'm totally new to vagrant AND I'm using a utility that depends on
> vagrant, so there is a layer of abstraction I'm dealing with to figure out
> why things aren't working.
>
> For context, I'm trying to install and use DetectionLab (
> https://github.com/clong/DetectionLab) which uses Vagrant.
>
> At this point, I don't know if the error is with Vagrant or with
> DetectionLab, so I beg your indulgence while I try to determine where the
> issue is.
>
> I have a Windows 10 laptop with 16GB RAM and VMware Workstation 15.x and
> everything is done under the admin account via an admin cli.
>
> Vagrant is installed on C: but the vagrantfile is located on E: (which has
> a ton of space).
>
> To prep, I downloaded and installed vagrant and purchased the vmware
> plugin as well.  But when I ran the command to build the Detectionlab
> machines I got the following error:
>
> 
> [preflight_checks] Checking for bad packer version..
> [preflight_checks] Checking if Vagrant is installed
> [preflight_checks] Checking for pre-existing boxes..
> [preflight_checks] Checking for vagrant instances..
> Vagrant encountered an error while attempting to load the utility
> service key file. This error can occur if the Vagrant VMware Utility
> has not yet been installed, or if it was installed incorrectly. If
> this error persists after running the Vagrant VMware Utility installer
> again, please contact support at: support email for hashicorp.com
>
> Information about the Vagrant VMware Utility, including installation
> instruction, can be found here:
>
>   https://www.vagrantup.com/docs/vmware/vagrant-vmware-utility.html
>
>   Path:
> C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-utility.client.crt
>   Error: No such file or directory @ rb_sysopen -
> C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-utility.client.crt
> preflight_checks : You appear to have already created at least one Vagrant
> instance. This script
> does not support already created instances. Please either destroy the
> existing instances or follow
> the build steps in the README to continue.
> At E:\DetectionLab-master\build.ps1:391 char:1
> + preflight_checks
> + 
> + CategoryInfo  : NotSpecified: (:) [Write-Error],
> WriteErrorException
> + FullyQualifiedErrorId :
> Microsoft.PowerShell.Commands.WriteErrorException,preflight_checks
>
> E:\>
>
>
> So I started checking vagrant to figure out if I did that part right:
>
>
> E:\DetectionLab-master>vagrant -v
> Vagrant 2.2.6
>
> C:\>vagrant plugin list
> vagrant-reload (0.0.1, global)
> vagrant-vmware-desktop (2.0.3, global)
>
> E:\DetectionLab-master>vagrant global-status
> id   name   provider state  directory
> 
> There are no active Vagrant environments on this computer! Or,
> you haven't destroyed and recreated Vagrant environments that were
> started with an older version of Vagrant.
>
> E:\DetectionLab-master>vagrant destroy
> Vagrant encountered an error while attempting to load the utility
> service key file. This error can occur if the Vagrant VMware Utility
> has not yet been installed, or if it was installed incorrectly. If
> this error persists after running the Vagrant VMware Utility installer
> again, please contact support at: support email for hashicorp.com
>
> Information about the Vagrant VMware Utility, including installation
> instruction, can be found here:
>
>   https://www.vagrantup.com/docs/vmware/vagrant-vmware-utility.html
>
>   Path:
> C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-utility.client.crt
>   Error: No such file or directory @ rb_sysopen -
> C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-utility.client.crt
>
>   E:\DetectionLab-master>vagrant box list
> There are no installed boxes! Use `vagrant box add` to add some.
>
> E:\DetectionLab-master>vagrant box prune
> There are no installed boxes! Use `vagrant box add` to add some.
>
>
> I uninstalled vagrant, rebooted, and re-installed Vagrant and got the
> exact same error.  I've googled "Vagrant encountered an error while
> attempting to load the utility service key file." and only got one hit and
> that was for a permission denied issue.  My Error is: "No such file or
> directory @ rb_sysopen"
>
> I had tried to do the DetectionLab install some months ago without
> purchasing the vmware plugin license, but it didn't work.  I deleted that
> directory when I started anew.  But it seems that Vagrant is still seeing
> that previous attempt?
>
> 

Re: [vagrant-up] How often are new releases of Vagrant built?

[Alvaro Miranda Aguilera]

you can monitor here for the new version to came out
https://releases.hashicorp.com/vagrant/

to check the cadence of releases, you could check the release dates on the
changelog
https://github.com/hashicorp/vagrant/blob/master/CHANGELOG.md


alvaro

On Wed, Jan 1, 2020 at 12:27 AM Bob Tanner  wrote:

> How often are new release of Vagrant built?
>
> Been 20 days since https://github.com/hashicorp/vagrant/issues/11249 was
> closed and I'd like to roll out VirtualBox 6.1.
>
>
> --
> 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/a79413ff-4e75-4ed5-9533-b01470970fa5%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/CAHqq0ex%3DhZ99kRfAxKYU_wF4sfqNuS-O%3DV-PwVc9hFctvnDPpg%40mail.gmail.com.

Re: [vagrant-up] Cannot restart my VM

[Alvaro Miranda Aguilera]

hello

where are the files you need to keep? on the directory on your machine ?
then you can copy them to ensure they wont be deleted or overwritten

if the files where local somewhere in the vm, try to open virtualbox gui,
and start the VM
once done, check over the gui console to login and check if the files are
still there, if yes, copy them


vagrant is to create disposable projects, depending on how this is
configured, the files may be on the host or the vm
the best is treat the VM as disposable and try to get some persistence on
your projects either by copy of the files. or control version.

good luck
alvaro

On Wed, Jan 1, 2020 at 6:07 PM kranai  wrote:

> Hi
>
> Recently I accidentally deleted some file in one of the virtual box
> directory because I saw a message that it could not rename a certain file
> because it did not clean during the last shutdown. But when I removed it
> and started "vagrant up" it went through and but when I tried to access my
> CMS wordpress site on my localhost machine at 192.168.33.10 it gave me a
> panel that shows it was going re-install my wordpress even though my
> wordpress files are intact.
>
> I was afraid to proceed because I fear that all my work done on my
> website/themes in my public folder on my laptop might get overwritten and I
> will lose a lot of work done.
>
> Can anyone please let me know how I can get back on track again: Below is
> the message I see when I do "vagrant up". I am running windows 10 (64bit).
>
> $ vagrant up
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'scotch/box'...
> ==> default: Matching MAC address for NAT networking...
> ==> default: Checking if box 'scotch/box' version '3.5' is up to date...
> ==> default: Setting the name of the VM: WPDistillery-Demo
> The name of your virtual machine couldn't be set because VirtualBox
> is reporting another VM with that name already exists. Most of the
> time, this is because of an error with VirtualBox not cleaning up
> properly. To fix this, verify that no VMs with that name do exist
> (by opening the VirtualBox GUI). If they don't, then look at the
> folder in the error message from VirtualBox below and remove it
> if there isn't any information you need in there.
> (P.s. I checked in my VB GUI there was no VMs with the same name)
> VirtualBox error:
>
> VBoxManage.exe: error: Could not rename the directory
> 'C:\Users\user\VirtualBox
> VMs\build-stuff_default_1496193404567_88071_1577851854867_22901' to
> 'C:\Users\user\VirtualBox VMs\WPDistillery-Demo' to save the settings file
> (VERR_ALREADY_EXISTS)
> VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component
> SessionMachine, interface IMachine, callee IUnknown
> VBoxManage.exe: error: Context: "SaveSettings()" at line 3206 of file
> VBoxManageModifyVM.cpp
>
> I submitted the above issue on *Vitrual Box forum* and below is the
> response :
> *"Vagrant does unexpected things with Virtualbox, so we don't support it
> here. You'll need to try Vagrant's forums."*
>
> I ping ponging now between vagrant and virtual box forums...
>
> can anybody help me get on track again without losing my work?
>
> Best Rgds
> Help much appreciated
>
> --
> 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/7e629441-82c2-41c2-ad1b-1a065a7fa146%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/CAHqq0ezf%3DKaxg5Hcb%3DxnH4UN%3DkB2ZD2ykaAXi2jLVCs7Z5p_Sw%40mail.gmail.com.

Re: [vagrant-up] Can only run as root. Why?

[Alvaro Miranda Aguilera]

Hello

if at some point you run vagrant with sudo, may explain this.

You can try to set all the files to be owned by your users at the project
directory (where you have the Vagrantfile) and the global vagrant firectory
/home/lasse/.vagrant.d

Thanks
Alvaro

On Sat, Dec 28, 2019 at 12:35 PM Lasse Karagiannis <
lasse.l.karagian...@gmail.com> wrote:

> Hi, I can only run "vagrant up" as root. I am on Ubuntu 18.04 and the
> vagrant box is "ubuntu/trusty64" System responds:
>
> Bringing machine 'default' up with 'virtualbox' provider...
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/environment.rb:589:in
>  `initialize': Permission denied @ rb_sysopen - 
> /home/lasse/.vagrant.d/data/lock.machine-action-8a592346e6d5c0439a627eece398466c.lock
>  (Errno::EACCES)
>   from 
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/environment.rb:589:in
>  `open'
>   from 
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/environment.rb:589:in
>  `block in lock'
>   from 
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/environment.rb:613:in
>  `lock'
>   from 
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/environment.rb:588:in
>  `lock'
>   from 
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:195:in
>  `call'
>   from 
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:195:in
>  `action'
>   from 
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/batch_action.rb:86:in
>  `block (2 levels) in run'
>
>
> --
> 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/b9fa180d-20d2-4d5f-baf1-d6c7bc609bfc%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/CAHqq0ewYnjkdUidmUA%3DQ7qrfMiJ847Cr_rOCCJZD-p5uDpwqxQ%40mail.gmail.com.

Re: [vagrant-up] WHile doing Vagrant up. i am getting the SSH new zero exit status

[Alvaro Miranda Aguilera]

can be used on linux

if you dont have dos2unix available you could try some different way, some
editors allow save on linux compatible format

try notepad++

good luck


alvaro

On Tue, Dec 24, 2019 at 11:12 AM Ravjot Singh  wrote:

> Yeah. i want to compare the bootstrap/install.sh and other files as well
> under bootstrap.
> but this command ie dos2unix  needs to used on windows right. and for that
> i need to install this also. how to do that in windows. i checked online
> and it shows only for Liinux
>
> On Tuesday, 24 December 2019 15:27:10 UTC+5:30, Alvaro Miranda Aguilera
> wrote:
>>
>> Hello
>>
>> You can learn more here:
>>
>>
>> https://unix.stackexchange.com/questions/32001/what-is-m-and-how-do-i-get-rid-of-it
>>
>>
>> basically there are characters in the script you are trying to run, that
>> in the VM are causing issues
>>
>> bootstrap/install.sh
>>
>>
>> alvaro
>>
>>
>> On Tue, Dec 24, 2019 at 10:48 AM Ravjot Singh  wrote:
>>
>>> I am not aware what are you saying.? dos2unix needs to be installed on
>>> windows right and which file to compare with this tool? and will this help?
>>>
>>>
>>>
>>> On Tuesday, 24 December 2019 15:10:48 UTC+5:30, Alvaro Miranda Aguilera
>>> wrote:
>>>>
>>>> hello
>>>>
>>>> this error
>>>>
>>>> ^M: bad interpreter:
>>>>
>>>> is cause when you edit files on windows and then run in linux, end of
>>>> line is different between the OS
>>>>
>>>> you will have to remove the end of line that are causing this, you can
>>>> try using a tool called dos2unix
>>>>
>>>> alvaro.
>>>>
>>>>
>>>>
>>>> On Tue, Dec 24, 2019 at 9:13 AM Ravjot Singh  wrote:
>>>>
>>>>> Please help on this.. When i run Vagrant up, i get the below error.
>>>>> Attaching the full logs as under :
>>>>> I did a vagrant reload to halt and start again and as it asked me to
>>>>> provision, so i ran the command vagrant provision.
>>>>>
>>>>> Any idea guys am i doing it correct???
>>>>>
>>>>>
>>>>> C:\BlockChain\devbox>*vagrant reload*
>>>>>
>>>>> ==> default: Attempting graceful shutdown of VM...
>>>>> ==> default: Checking if box 'ubuntu/xenial64' version '20191211.0.0'
>>>>> is up to date...
>>>>> ==> default: Clearing any previously set forwarded ports...
>>>>> ==> default: Clearing any previously set network interfaces...
>>>>> ==> default: Preparing network interfaces based on configuration...
>>>>> default: Adapter 1: nat
>>>>> ==> default: Forwarding ports...
>>>>> default: 8080 (guest) => 8080 (host) (adapter 1)
>>>>> default: 4000 (guest) => 4000 (host) (adapter 1)
>>>>> default: 22 (guest) =>  (host) (adapter 1)
>>>>> ==> default: Running 'pre-boot' VM customizations...
>>>>> ==> default: Booting VM...
>>>>> ==> default: Waiting for machine to boot. This may take a few
>>>>> minutes...
>>>>> default: SSH address: 127.0.0.1:
>>>>> default: SSH username: vagrant
>>>>> default: SSH auth method: private key
>>>>> ==> default: Machine booted and ready!
>>>>> [default] GuestAdditions 6.0.14 running --- OK.
>>>>> ==> default: Checking for guest additions in VM...
>>>>> ==> default: Mounting shared folders...
>>>>> default: /vagrant => C:/BlockChain/devbox
>>>>> default: /home/vagrant/bootstrap => C:/BlockChain/devbox/bootstrap
>>>>> ==> default: Machine already provisioned. Run `vagrant provision` or
>>>>> use the `--provision`
>>>>> ==> default: flag to force provisioning. Provisioners marked to run
>>>>> always will still run.
>>>>>
>>>>> C:\BlockChain\devbox>*vagrant provision*
>>>>> ==> default: Running provisioner: shell...
>>>>> default: Running: inline script
>>>>> default: /tmp/vagrant-shell: /home/vagrant/bootstrap/install.sh:
>>>>> /bin/bash^M: bad interpreter: No such file or directory
>>>>> The SSH command responded with a non-zero exit status. Vagrant
>>>>> assumes

Re: [vagrant-up] WHile doing Vagrant up. i am getting the SSH new zero exit status

[Alvaro Miranda Aguilera]

Hello

You can learn more here:

https://unix.stackexchange.com/questions/32001/what-is-m-and-how-do-i-get-rid-of-it


basically there are characters in the script you are trying to run, that in
the VM are causing issues

bootstrap/install.sh


alvaro


On Tue, Dec 24, 2019 at 10:48 AM Ravjot Singh  wrote:

> I am not aware what are you saying.? dos2unix needs to be installed on
> windows right and which file to compare with this tool? and will this help?
>
>
>
> On Tuesday, 24 December 2019 15:10:48 UTC+5:30, Alvaro Miranda Aguilera
> wrote:
>>
>> hello
>>
>> this error
>>
>> ^M: bad interpreter:
>>
>> is cause when you edit files on windows and then run in linux, end of
>> line is different between the OS
>>
>> you will have to remove the end of line that are causing this, you can
>> try using a tool called dos2unix
>>
>> alvaro.
>>
>>
>>
>> On Tue, Dec 24, 2019 at 9:13 AM Ravjot Singh  wrote:
>>
>>> Please help on this.. When i run Vagrant up, i get the below error.
>>> Attaching the full logs as under :
>>> I did a vagrant reload to halt and start again and as it asked me to
>>> provision, so i ran the command vagrant provision.
>>>
>>> Any idea guys am i doing it correct???
>>>
>>>
>>> C:\BlockChain\devbox>*vagrant reload*
>>>
>>> ==> default: Attempting graceful shutdown of VM...
>>> ==> default: Checking if box 'ubuntu/xenial64' version '20191211.0.0' is
>>> up to date...
>>> ==> default: Clearing any previously set forwarded ports...
>>> ==> default: Clearing any previously set network interfaces...
>>> ==> default: Preparing network interfaces based on configuration...
>>> default: Adapter 1: nat
>>> ==> default: Forwarding ports...
>>> default: 8080 (guest) => 8080 (host) (adapter 1)
>>> default: 4000 (guest) => 4000 (host) (adapter 1)
>>> default: 22 (guest) =>  (host) (adapter 1)
>>> ==> default: Running 'pre-boot' VM customizations...
>>> ==> default: Booting VM...
>>> ==> default: Waiting for machine to boot. This may take a few minutes...
>>> default: SSH address: 127.0.0.1:
>>> default: SSH username: vagrant
>>> default: SSH auth method: private key
>>> ==> default: Machine booted and ready!
>>> [default] GuestAdditions 6.0.14 running --- OK.
>>> ==> default: Checking for guest additions in VM...
>>> ==> default: Mounting shared folders...
>>> default: /vagrant => C:/BlockChain/devbox
>>> default: /home/vagrant/bootstrap => C:/BlockChain/devbox/bootstrap
>>> ==> default: Machine already provisioned. Run `vagrant provision` or use
>>> the `--provision`
>>> ==> default: flag to force provisioning. Provisioners marked to run
>>> always will still run.
>>>
>>> C:\BlockChain\devbox>*vagrant provision*
>>> ==> default: Running provisioner: shell...
>>> default: Running: inline script
>>> default: /tmp/vagrant-shell: /home/vagrant/bootstrap/install.sh:
>>> /bin/bash^M: bad interpreter: No such file or directory
>>> The SSH command responded with a non-zero exit status. Vagrant
>>> assumes that this means the command failed. The output for this command
>>> should be in the log above. Please read the output to determine what
>>> went wrong.
>>>
>>> --
>>> 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/392f8fe4-2db6-45dc-af44-af73a8d89cab%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/392f8fe4-2db6-45dc-af44-af73a8d89cab%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> Alvaro
>>
>> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> ht

Re: [vagrant-up] How to change Vagrant box in Windows?

[Alvaro Miranda Aguilera]

by default all of the ones defined in vagrantfile

you can do

vagrant status

and will show the boxes

if you want to start only 1, you can try vagrant up 

alvaro

On Tue, Dec 17, 2019 at 7:38 AM 'Jason Long' via Vagrant <
vagrant-up@googlegroups.com> wrote:

> Thank you.
> When I use "vagrant up" command then which boxes launched?
>
> On Monday, December 16, 2019, 11:31:21 PM GMT+3:30, Alvaro Miranda
> Aguilera  wrote:
>
>
> vagrant status
>
> then vagrant ssh 
>
> alvaro
>
> On Mon, Dec 16, 2019 at 8:31 PM 'Jason Long' via Vagrant <
> vagrant-up@googlegroups.com> wrote:
>
> Hello,
> I installed the last version of Vagrant on Windows OS and then installed
> two VMs: 1-Debian/Jessie 2-CentOS/7
> How can I select and run specific VM?
>
> 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/216745869.5621392.1576524677927%40mail.yahoo.com
> <https://groups.google.com/d/msgid/vagrant-up/216745869.5621392.1576524677927%40mail.yahoo.com?utm_medium=email_source=footer>
> .
>
>
>
> --
> 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/CAHqq0eyRh9DQnrbFssDgLM9kMtJXbSCuCjnv%3D15b1ELSi0hATw%40mail.gmail.com
> <https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyRh9DQnrbFssDgLM9kMtJXbSCuCjnv%3D15b1ELSi0hATw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> --
> 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/634295661.96463.1576564727519%40mail.yahoo.com
> <https://groups.google.com/d/msgid/vagrant-up/634295661.96463.1576564727519%40mail.yahoo.com?utm_medium=email_source=footer>
> .
>


-- 
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/CAHqq0ewvZ8mpay3Prc1wd6r081-GhuDDamroqV_wrN%3Dtb5HA3g%40mail.gmail.com.

Re: [vagrant-up] Support for VirtualBox 6.1

[Alvaro Miranda Aguilera]

will be on the next release.

https://github.com/hashicorp/vagrant/blob/master/CHANGELOG.md

I don't have an strong ETA, but i would say somewhere in january

Alvaro

On Wed, Dec 18, 2019 at 5:28 PM Tomás Garrido  wrote:

> When do you plan to add support for VirtualBox 6.1 in Vagrant?  I'm using
> 2.2.6 and it doesn't support VirtualBox 6.1
> Thanks.
>
> --
> 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/d258af99-e3df-47be-8cb5-0be309591394%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/CAHqq0extbnAZBfrTJ184g2EFRN5uYLU%2BRF3iQqyue1a%2Byy8p4w%40mail.gmail.com.

Re: [vagrant-up] Vagrant up fails with `require': cannot load such file -- winrm (LoadError)

[Alvaro Miranda Aguilera]

share the vagrantfile you are using the output of vagrant plugin list

if you are on fedora, then the vagrantfile seems to be trying to run
parallels that is virtualization for macos

so please also confirm your host os.


alvaro

On Wed, Dec 18, 2019 at 11:45 AM Gaurav Talreja 
wrote:

> Hi everyone,
>
> When I try to `vagrant up --no-provision` a Windows Vagrant box I get the 
> following error:
>
> ```
> '2019-12-17 09:30:28,204 INFO  Executing: Process "vagrant up 
> --no-provision --parallel"
> 2019-12-17 09:30:33,600DEBUG  
> /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require': 
> cannot load such file -- winrm (LoadError)
> 2019-12-17 09:30:33,602DEBUG  from 
> /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require'
> 2019-12-17 09:30:33,602DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/plugins/communicators/winrm/shell.rb:9:in
>  `block in '
> 2019-12-17 09:30:33,602DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/util/silence_warnings.rb:8:in
>  `silence!'
> 2019-12-17 09:30:33,602DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/plugins/communicators/winrm/shell.rb:8:in
>  `'
> 2019-12-17 09:30:33,603DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/plugins/communicators/winrm/communicator.rb:6:in
>  `require_relative'
> 2019-12-17 09:30:33,603DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/plugins/communicators/winrm/communicator.rb:6:in
>  `'
> 2019-12-17 09:30:33,603DEBUG  from 
> /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require'
> 2019-12-17 09:30:33,603DEBUG  from 
> /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require'
> 2019-12-17 09:30:33,603DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/plugins/communicators/winrm/plugin.rb:15:in
>  `block in '
> 2019-12-17 09:30:33,603DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/registry.rb:27:in `get'
> 2019-12-17 09:30:33,603DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/machine.rb:259:in 
> `communicate'
> 2019-12-17 09:30:33,603DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/machine.rb:141:in 
> `initialize'
> 2019-12-17 09:30:33,604DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/vagrantfile.rb:81:in 
> `new'
> 2019-12-17 09:30:33,604DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/vagrantfile.rb:81:in 
> `machine'
> 2019-12-17 09:30:33,604DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/environment.rb:715:in 
> `machine'
> 2019-12-17 09:30:33,604DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/plugin/v2/command.rb:180:in
>  `block in with_target_vms'
> 2019-12-17 09:30:33,604DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/plugin/v2/command.rb:204:in
>  `block in with_target_vms'
> 2019-12-17 09:30:33,604DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/plugin/v2/command.rb:186:in
>  `each'
> 2019-12-17 09:30:33,604DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/plugin/v2/command.rb:186:in
>  `with_target_vms'
> 2019-12-17 09:30:33,605DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/plugins/commands/up/command.rb:87:in
>  `execute'
> 2019-12-17 09:30:33,605DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/cli.rb:66:in `execute'
> 2019-12-17 09:30:33,605DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/environment.rb:290:in 
> `cli'
> 2019-12-17 09:30:33,605DEBUG  from 
> /usr/share/vagrant/gems/gems/vagrant-2.2.5/bin/vagrant:182:in ` (required)>'
> 2019-12-17 09:30:33,605DEBUG  from 
> /usr/share/vagrant/gems/bin/vagrant:23:in `load'
> 2019-12-17 09:30:33,605DEBUG  from 
> /usr/share/vagrant/gems/bin/vagrant:23:in `'
>
> ```
>
>
> I'm using,
>
> vagrant-2.2.5-1.fc30.noarch
>
> vagrant-libvirt (0.0.45, system)
>
> vagrant-sshfs (1.3.1, system)
>
> also tried with vagrant-2.2.6
>
>
> can anyone help me with this issue?
>
>
> --
> 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/aa888df6-fc7b-43dd-b16b-e31c36068559%40googlegroups.com
> 

Re: [vagrant-up] WHile doing Vagrant up. i am getting the SSH new zero exit status

[Alvaro Miranda Aguilera]

hello

this error

^M: bad interpreter:

is cause when you edit files on windows and then run in linux, end of line
is different between the OS

you will have to remove the end of line that are causing this, you can try
using a tool called dos2unix

alvaro.



On Tue, Dec 24, 2019 at 9:13 AM Ravjot Singh  wrote:

> Please help on this.. When i run Vagrant up, i get the below error.
> Attaching the full logs as under :
> I did a vagrant reload to halt and start again and as it asked me to
> provision, so i ran the command vagrant provision.
>
> Any idea guys am i doing it correct???
>
>
> C:\BlockChain\devbox>*vagrant reload*
>
> ==> default: Attempting graceful shutdown of VM...
> ==> default: Checking if box 'ubuntu/xenial64' version '20191211.0.0' is
> up to date...
> ==> default: Clearing any previously set forwarded ports...
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> ==> default: Forwarding ports...
> default: 8080 (guest) => 8080 (host) (adapter 1)
> default: 4000 (guest) => 4000 (host) (adapter 1)
> default: 22 (guest) =>  (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:
> default: SSH username: vagrant
> default: SSH auth method: private key
> ==> default: Machine booted and ready!
> [default] GuestAdditions 6.0.14 running --- OK.
> ==> default: Checking for guest additions in VM...
> ==> default: Mounting shared folders...
> default: /vagrant => C:/BlockChain/devbox
> default: /home/vagrant/bootstrap => C:/BlockChain/devbox/bootstrap
> ==> default: Machine already provisioned. Run `vagrant provision` or use
> the `--provision`
> ==> default: flag to force provisioning. Provisioners marked to run always
> will still run.
>
> C:\BlockChain\devbox>*vagrant provision*
> ==> default: Running provisioner: shell...
> default: Running: inline script
> default: /tmp/vagrant-shell: /home/vagrant/bootstrap/install.sh:
> /bin/bash^M: bad interpreter: No such file or directory
> The SSH command responded with a non-zero exit status. Vagrant
> assumes that this means the command failed. The output for this command
> should be in the log above. Please read the output to determine what
> went wrong.
>
> --
> 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/392f8fe4-2db6-45dc-af44-af73a8d89cab%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/CAHqq0eywcTmNdzHNHccVv4M-UoWELQUJ%3DSwJKYQ67BEExmFhuA%40mail.gmail.com.

Re: [vagrant-up] Connecting ALSA from a VM to the host?

[Alvaro Miranda Aguilera]

hello

you need to do that just once to see what are the settings you need

then you can codify what is needed as part of the vagrantfile

make sense ?

i was suggesting the first step, make it work

then we can review how to codify / make it part of the vagrantfile

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/CAHqq0ewJoYEe9rA6WdpJ7ktV3pzGva2vM0aGPfPyafWy0962dg%40mail.gmail.com.

Re: [vagrant-up] How to change Vagrant box in Windows?

[Alvaro Miranda Aguilera]

vagrant status

then vagrant ssh 

alvaro

On Mon, Dec 16, 2019 at 8:31 PM 'Jason Long' via Vagrant <
vagrant-up@googlegroups.com> wrote:

> Hello,
> I installed the last version of Vagrant on Windows OS and then installed
> two VMs: 1-Debian/Jessie 2-CentOS/7
> How can I select and run specific VM?
>
> 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/216745869.5621392.1576524677927%40mail.yahoo.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/CAHqq0eyRh9DQnrbFssDgLM9kMtJXbSCuCjnv%3D15b1ELSi0hATw%40mail.gmail.com.

Re: [vagrant-up] Connecting ALSA from a VM to the host?

[Alvaro Miranda Aguilera]

vagrant is just a wrapper

once the vm has been created, you can stop the vm with vagrant halt

then go to the VM settings in virtualbox and add whatever you think is
needed ie a sound card

once this is done, turn the VM on and test the sound.

as long the virtualbox guest additions are installed and you have some sort
of mixer on the vm to adjust audio it should work

then you can either export the VM and have it as a new base box

or

you can use VBoxManage to add the sound card you need.

you can customize the box like this
https://www.vagrantup.com/docs/virtualbox/configuration.html#vboxmanage-customizations


alvaro.

On Fri, Dec 13, 2019 at 3:33 AM Rich Morin  wrote:

> Having switched from OSS to ALSA, I've made some progress, but I'm still
> not getting sound.  By way of background, I'm doing my development and
> testing on a MacBook Air, running macOS High Sierra (10.13.6).  As I
> recently posted on the ALSA list:
>
> > I've successfully built a VirtualBox instance, based on Ubuntu, for use
> under Vagrant.  Now I'd like to set up ALSA to use the host's audio output
> system.  Making things more complicated, the host could be running Linux,
> macOS, Windows, or ???
>
> I reworked my Vagrantfile to incorporate some ideas from Christoph
> Neumann's vagrant-audio Vagrantfile (in
> https://github.com/christoph-neumann/vagrant-audio).  For details, see
> this gist:
>
>  https://gist.github.com/RichMorin/dc9138962c19c205697bea23cce5134c
>
> After building the VM, I can SSH into it via `vagrant ssh`.
>
> If I then run `speaker-test`, the program prints out some promising text
> and then hangs:
>
>  vagrant@vagrant:~$ speaker-test
>  speaker-test 1.1.8
>
>  Playback device is default
>  Stream parameters are 48000Hz, S16_LE, 1 channels
>  Using 16 octaves of pink noise
>  Rate set to 48000Hz (requested 48000Hz)
>  Buffer size range from 69 to 17832
>  Period size range from 34 to 8917
>  Using max buffer size 17832
>  Periods = 4
>  was set period_size = 4458
>  was set buffer_size = 17832
>   0 - Front Left
>
> And, if I do `aplay -L`, I get:
>
>  vagrant@vagrant:~$ aplay -L
>  null
>Discard all samples (playback) or generate zero samples (capture)
>  default
>  sysdefault:CARD=Intel
>HDA Intel, STAC9221 A1 Analog
>Default Audio Device
>  front:CARD=Intel,DEV=0
>HDA Intel, STAC9221 A1 Analog
>Front speakers
>  ...
>
> Helpful clues, comments, and suggestions are solicited.
>
> -r
>
> --
> 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/84D2FD0F-EE3E-4082-AB60-30C84DAFDFF4%40cfcl.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/CAHqq0ezRPrzcHyaSWcSgFMdbVGP7pttBOLD6ow%3DHAGv%2Buh7NpQ%40mail.gmail.com.

Re: [vagrant-up] How to take backup of Vagrant box without reboot ?

[Alvaro Miranda Aguilera]

hello

i would suggest review the way you are doing this and try see it using the
right tools

you could replace vagrant with terraform to manage such environment.

and you could use source control to manage any change to infra or app
running.

if anything goes wrong you just recreate everything and deploy latest
changes.

if there is anything you need to have backups, then i am not sure this is
dev or qa as seems more like a prod

how you handle prod? i would assume is a problem solved since you may need
business continuity


On Sat, Nov 30, 2019 at 9:19 PM Adminbirds  wrote:

> Our Dev & QA infra setups are made with vagrant box.
>
> It configured on 4 physical Dell server's, with 33 vms - CentOS
>
> most of the vm's are MySQL mongo nginx Kafka elastic search ,Apache storm
> etc.
>
>
> if anything goes wrong main physical servers,we need to recover all the
> vm's so need the snapshot of that vm's as package for quick recovery..just
> like aws ami/snapshots
>
>
>
>
>
> On Sat 30 Nov, 2019, 7:10 AM Alvaro Miranda Aguilera, 
> wrote:
>
>> why you need backups of vagrant vms ?
>>
>>
>> On Tue, Nov 26, 2019 at 8:59 AM Adminbirds  wrote:
>>
>>> Hi
>>>
>>> we have 33 vagrant box running on our physical machine. I need to take
>>> entire VM backup to our backup server.
>>>
>>> I found this
>>>
>>>
>>> https://scotch.io/tutorials/how-to-create-a-vagrant-base-box-from-an-existing-one
>>>
>>> Creating as package then copy it to remote location (vagrant package).
>>> But while doing vagrant package the box went down, is there is any option
>>> to take vagrant package with --no-reboot option.
>>>
>>> For 100 GB box it took more than 2 hours to converting as package. we
>>> can't afford downtime :-)
>>>
>>> One more question, I'm copying the current vmdk files & to remote
>>> folder, VM's is in running state, does it cause any data corruption for the
>>> box ? while syncing the data to remote location.
>>>
>>> Simply my question is how we can take entire vm box backup without
>>> reboot box ? anybody knows the answer, please help ;-)
>>>
>>> --
>>> 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/add0d9ca-0089-42b8-a426-0b4c04278c72%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/add0d9ca-0089-42b8-a426-0b4c04278c72%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> 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/CAHqq0ezKrEkMh2PpspZcNZifR5qeiKqsxQRbycjmv%2B40uy3jHQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezKrEkMh2PpspZcNZifR5qeiKqsxQRbycjmv%2B40uy3jHQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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 gro

Re: [vagrant-up] vagrant plugin install from a local file source without internet connection

[Alvaro Miranda Aguilera]

uot;]
> DEBUG bundler: Activating gem excon-0.68.0
> DEBUG bundler: Activating gem formatador-0.2.5
> DEBUG bundler: Activating gem fog-core-1.43.0
> DEBUG bundler: Activating gem fog-json-1.2.0
> DEBUG bundler: Activating gem ruby-libvirt-0.7.1
> DEBUG bundler: Activating gem mini_portile-0.5.0
> DEBUG bundler: Activating gem nokogiri-1.6.0
> DEBUG bundler: Activating gem fog-xml-0.1.3
> DEBUG bundler: Activating gem fog-libvirt-0.7.0
> DEBUG bundler: Activating gem vagrant-libvirt-0.0.45
>  INFO manager: Loading plugins...
>  INFO manager: Loading plugin `builder` with default require: `builder`
> DEBUG manager: Successfully loaded plugin `builder`.
>  INFO manager: Loading plugin `excon` with default require: `excon`
> DEBUG manager: Successfully loaded plugin `excon`.
>  INFO manager: Loading plugin `fog-core` with default require: `fog-core`
> ERROR manager: Failed to load plugin `fog-core` with default require. -
> LoadError: cannot load such file -- fog-core
>  INFO manager: Loading plugin `fog-core` with slash require: `fog/core`
> DEBUG manager: Successfully loaded plugin `fog-core`.
>  INFO manager: Loading plugin `fog-json` with default require: `fog-json`
> ERROR manager: Failed to load plugin `fog-json` with default require. -
> LoadError: cannot load such file -- fog-json
>  INFO manager: Loading plugin `fog-json` with slash require: `fog/json`
> DEBUG manager: Successfully loaded plugin `fog-json`.
>  INFO manager: Loading plugin `fog-libvirt` with default require:
> `fog-libvirt`
> ERROR manager: Failed to load plugin `fog-libvirt` with default require. -
> LoadError: cannot load such file -- fog-libvirt
>  INFO manager: Loading plugin `fog-libvirt` with slash require:
> `fog/libvirt`
> DEBUG manager: Successfully loaded plugin `fog-libvirt`.
>  INFO manager: Loading plugin `fog-xml` with default require: `fog-xml`
> ERROR manager: Failed to load plugin `fog-xml` with default require. -
> LoadError: cannot load such file -- fog-xml
>  INFO manager: Loading plugin `fog-xml` with slash require: `fog/xml`
> DEBUG manager: Successfully loaded plugin `fog-xml`.
>  INFO manager: Loading plugin `formatador` with default require:
> `formatador`
> DEBUG manager: Successfully loaded plugin `formatador`.
>  INFO manager: Loading plugin `mime-types` with default require:
> `mime-types`
> DEBUG manager: Successfully loaded plugin `mime-types`.
>  INFO manager: Loading plugin `mime-types-data` with default require:
> `mime-types-data`
> DEBUG manager: Successfully loaded plugin `mime-types-data`.
>  INFO manager: Loading plugin `mini_portile` with default require:
> `mini_portile`
> DEBUG manager: Successfully loaded plugin `mini_portile`.
>  INFO manager: Loading plugin `multi_json` with default require:
> `multi_json`
> DEBUG manager: Successfully loaded plugin `multi_json`.
>  INFO manager: Loading plugin `nokogiri` with default require: `nokogiri`
> DEBUG manager: Successfully loaded plugin `nokogiri`.
>  INFO manager: Loading plugin `ruby-libvirt` with default require:
> `ruby-libvirt`
> ERROR manager: Failed to load plugin `ruby-libvirt` with default require.
> - LoadError: cannot load such file -- ruby-libvirt
>  INFO manager: Loading plugin `ruby-libvirt` with slash require:
> `ruby/libvirt`
> ERROR manager: Plugin loading error: LoadError - cannot load such file --
> ruby/libvirt
> DEBUG manager:
> /opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
> `require'
> DEBUG manager:
> /opt/vagrant/embedded/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
> `require'
> DEBUG manager:
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/plugin/manager.rb:322:in
> `rescue in block in load_plugins'
> DEBUG manager:
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/plugin/manager.rb:314:in
> `block in load_plugins'
> DEBUG manager:
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/plugin/manager.rb:312:in
> `each'
> DEBUG manager:
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/plugin/manager.rb:312:in
> `load_plugins'
> DEBUG manager:
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/environment.rb:176:in
> `initialize'
> DEBUG manager:
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/bin/vagrant:145:in `new'
> DEBUG manager:
> /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/bin/vagrant:145:in
> `'
> ERROR vagrant: Vagrant experienced an error! Details:
> ERROR vagrant: # load properly. The error message given is
> shown below.
>
> cannot load such file -- ruby/libvirt>
> ERROR vagrant: The plugins failed to load properly. The error message
> given is
> shown below.
>
> cannot load such file 

Re: [vagrant-up] How to take backup of Vagrant box without reboot ?

[Alvaro Miranda Aguilera]

why you need backups of vagrant vms ?


On Tue, Nov 26, 2019 at 8:59 AM Adminbirds  wrote:

> Hi
>
> we have 33 vagrant box running on our physical machine. I need to take
> entire VM backup to our backup server.
>
> I found this
>
>
> https://scotch.io/tutorials/how-to-create-a-vagrant-base-box-from-an-existing-one
>
> Creating as package then copy it to remote location (vagrant package). But
> while doing vagrant package the box went down, is there is any option to
> take vagrant package with --no-reboot option.
>
> For 100 GB box it took more than 2 hours to converting as package. we
> can't afford downtime :-)
>
> One more question, I'm copying the current vmdk files & to remote folder,
> VM's is in running state, does it cause any data corruption for the box ?
> while syncing the data to remote location.
>
> Simply my question is how we can take entire vm box backup without reboot
> box ? anybody knows the answer, please help ;-)
>
> --
> 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/add0d9ca-0089-42b8-a426-0b4c04278c72%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/CAHqq0ezKrEkMh2PpspZcNZifR5qeiKqsxQRbycjmv%2B40uy3jHQ%40mail.gmail.com.

Re: [vagrant-up] vagrant plugin install from a local file source without internet connection

[Alvaro Miranda Aguilera]

hello

how did you install the dependencies?

whats the output of
vagrant plugin list

thanks
alvaro

On Tue, Nov 26, 2019 at 5:10 AM sahana Santhosh 
wrote:

> Hi Alvaro,
>
> Thanks for the response I tried but faced the same issue
>
> # vagrant plugin install ./vagrant-libvirt-0.0.45.gem
>
> Installing the './vagrant-libvirt-0.0.45.gem' plugin. This can take a few
> minutes...
> Vagrant failed to load a configured plugin source. This can be caused
> by a variety of issues including: transient connectivity issues, proxy
> filtering rejecting access to a configured plugin source, or a configured
> plugin source not responding correctly. Please review the error message
> below to help resolve the issue:
>
>   no such name (https://gems.hashicorp.com/specs.4.8.gz)
>
> Source: https://gems.hashicorp.com/
>
>
> However I am able to install with command
> "vagrant plugin install --plugin-clean-sources vagrant-libvirt-0.0.45.gem"
>
> but after the installation " vagrant box add test test.box"  failed with
> following error
>
>  INFO manager: Loading plugin `ruby-libvirt` with slash require:
> `ruby/libvirt`
> ERROR manager: Plugin loading error: LoadError - cannot load such file --
> ruby/libvirt
>
>
> I did install all the dependencies needed for  vagrant-libvirt like
> [formatador-0.2.5.gem,
> excon-0.68.0.gem,builder-3.2.3.gem,fog-core-1.43.0.gem,fog-json-1.2.0.gem
> ,fog-libvirt-0.7.0.gem,fog-xml-0.1.3.gem ,
> mini_portile-0.5.0.gem,multi_json-1.14.1.gem,nokogiri-1.6.0.gem,ruby-libvirt-0.7.1.gem]
> .
> I am not sure if the above way of installing the plugin is correct or not.
> Please guide.
>
>
>
> On Tuesday, November 26, 2019 at 2:55:22 AM UTC+5:30, Alvaro Miranda
> Aguilera wrote:
>>
>> hello try
>>
>> vagrant plugin install ./vagrant-libvirt-0.0.45.gem
>>
>> On Wed, Nov 20, 2019 at 9:41 AM sahana Santhosh 
>> wrote:
>>
>>> Hi,
>>>
>>> I am trying to install vagrant plugin "vagrant-libvirt". I have
>>> downloaded all the necessary .gem file in my local machine which does not
>>> have access to internet. I am facing the following error...
>>>
>>> # vagrant plugin install vagrant-libvirt-0.0.45.gem
>>>
>>> Installing the 'vagrant-libvirt-0.0.45.gem' plugin. This can take a few
>>> minutes...
>>>
>>> Vagrant failed to load a configured plugin source. This can be caused
>>> by a variety of issues including: transient connectivity issues, proxy
>>> filtering rejecting access to a configured plugin source, or a configured
>>> plugin source not responding correctly. Please review the error message
>>> below to help resolve the issue:
>>>
>>>   no such name (https://gems.hashicorp.com/specs.4.8.gz)
>>>
>>> Source: https://gems.hashicorp.com/
>>>
>>>
>>>
>>> Why it is trying to access internet when we are pointing it to local gem
>>> file ?? Is it possible to install vagrant plugin offline ? This is bottle
>>> neck for us, please let us know if offline installation is possible or not.
>>>
>>> Thanks in advance
>>>
>>> -Sahana
>>>
>>> --
>>> 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/4454c8d3-c52d-4ac1-8fb5-bdabf8b29428%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/4454c8d3-c52d-4ac1-8fb5-bdabf8b29428%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> 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 Go

Re: [vagrant-up] Re: Spinning up a few docker containers in Windows host + Vagrant + Virtualbox environment

[Alvaro Miranda Aguilera]

yes

and you can use private network to have connectivity between vms.

for vm to vm in docker to docker, it seems the best is create 2 nodes on
docker swarm.. just not sure whats the best for your setup

alvaro

On Sun, Oct 13, 2019 at 12:53 AM Sorcerer Stone 
wrote:

> Hmm, I googled. I think the instructions on this URL seems to be the
> solution I am looking for.
>
> https://www.vagrantup.com/docs/multi-machine/
>
> Am I correct?
>
>
> On Saturday, October 12, 2019 at 5:22:46 PM UTC-4, Sorcerer Stone wrote:
>>
>> In native Windows environment, I can use dos boxes to access docker
>> (docker toolbox + Virtualbox) so that I can run one docker container
>> against another related container.
>>
>> My OS is Win10 pro (with HyperV disabled), Running a Linux environment
>> using Vagrant & Virtualbox. So I am within a guest Ubuntu host and I want
>> to do something similar to the above aka run multiple docker containers
>> (i.e. I would like to run a docker container to interact with the existing
>> running container. How do I achieve in Vagrant environment?
>> In my host folder, I have a vagrantfile which tells the virtual host to
>> load Ubuntu using Vagrant Up and then I run a docker container. I can't
>> possibly pull up another dos box and try to access the same virtual
>> environment by running the same vagrantfile so that I can run another
>> docker container. Correct?
>> Can anyone please advise me how I can run multiple docker containers in
>> this mixed Vagrant, Virtualbox, environment? I need 2 docker containers
>> running side-by-side and interacting with each other.
>> Thanks in advance.
>>
>> --
> 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/dea7cc4d-48b4-4bd2-a421-e1124200eba3%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/CAHqq0ez%2BtAzSY_mF4-51AyKHTp-CeyJYcUtZ36mH1V9%2BnjYuQQ%40mail.gmail.com.

Re: [vagrant-up] [Vagrant 2.2.5] [Hyper-V] Guest-specific operations were attempted on a machine that is not ready for guest communication.

[Alvaro Miranda Aguilera]

hello

vagrant-vbguest is for virtualbox guest additions

i would suggest remove this and other plugins if not using virtualbox

the vm seems already was provisioned, so maybe did work at some point

you could try

vagrant destroy
vagrant up

if still fails, check hyper v console of this vm to check what may be
happening

alvaro

On Wed, Oct 16, 2019 at 8:30 PM Jacqueline Costa 
wrote:

> Well,
>
> I am using vagrant 2.2.5 and also provider is HyperV, I am using Stefan's
> Windows 10 box  
> But when one of my shell scripts start to working vagrant return:
>
> Bringing machine 'hyperv' up with 'hyperv' provider...
>
> ==> hyperv: Verifying Hyper-V is enabled...
>
> ==> hyperv: Verifying Hyper-V is accessible...
>
> ==> hyperv: Machine already provisioned.
>
> Run `vagrant provision` or use the `--provision`
>
> ==> hyperv: flag to force provisioning.
>
> Provisioners marked to run always will still run.
>
> ==> hyperv: Running provisioner: shell...
>
>
> Guest-specific operations were attempted on a machine that is not ready for 
> guest communication. This should not happen and a bug should be reported
>
>
> I tried install the plugin vagrant-vbguest and also without it, but the both 
> ways returns the message of Guest-specific.
>
> Any idea of what is happening?
>
> --
> 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/5318a3c5-df79-40b5-805a-0d7e791b794d%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/CAHqq0eze545G6QUDK76oM5%3DDNU1iPjN%3D2nwkysBNco2Q9cdNPg%40mail.gmail.com.

Re: [vagrant-up] how to create vm with existing vmdk file

[Alvaro Miranda Aguilera]

hello

did you found a reply to your question?


On Thu, Oct 10, 2019 at 4:11 PM Adminbirds  wrote:

> Hi
>
> I need to create a vm with existing vmdk file, base machine is centos, How
> to do in command line
>
> I tried box not up due to UUID mismatch, I have updated .vbox .xml file
> after creating new UUID, no luck
>
> --
> 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/fbd2ad48-06fc-4978-9d1e-e16c9fb980ee%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/CAHqq0ezfg6NeCa9UhLq0G4qeMfpEY4n8i0uDrWD4vBTN1rZLFQ%40mail.gmail.com.

Re: [vagrant-up] Run local exec after digitalocean droplet

[Alvaro Miranda Aguilera]

hello

sorry for the late reply

this is the vagrant mailing list

do you have a vagrant question?

On Tue, Oct 15, 2019 at 11:09 AM Julian Zielke 
wrote:

> Hi,
>
> I'm currently using Terragrunt in combination with Terraform to deploy
> digitalocean droplets.
>
> What I'm planning is to use local exec in order to run Ansbile on the
> deployed host(s) afterwards. So I need to access the list of hosts somehow
> but I always run into an error
> saying that the variable xyz is not (yet) declared.
>
> Here's an Example I've tried:
>
> resource "digitalocean_droplet" "instance" {
>  image = "${var.host_image}"
>  name  = "${var.host_name}"
>  region= "fra1"
>  size  = "${var.host_sizing}"
>  backups   = "${var.useBackups}"
>  tags  = "${split(",", replace(var.host_tags, " ", ""))}"
>  ssh_keys  = ["${digitalocean_ssh_key.default.fingerprint}"]
>  provisioner "remote-exec" {
>inline = ["echo"]
>
> connection {
>  host= "${data.digitalocean_droplet.instance.ipv4_address}"
>  type= "ssh"
>  user= "root"
>  private_key = "${file(var.public_key)}"
>}
>  }
> }
>
> Any chance to accomplish my goal?
>
> --
> 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/65cec1b4-203f-4f0d-bb96-5c9e8e5e137e%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/CAHqq0ez8_GjdAdKts36%3Dupbq2PTXNVHik%3DFukV8jeEK9WfWaVg%40mail.gmail.com.

Re: [vagrant-up] vagrant plugin install from a local file source without internet connection

[Alvaro Miranda Aguilera]

hello try

vagrant plugin install ./vagrant-libvirt-0.0.45.gem

On Wed, Nov 20, 2019 at 9:41 AM sahana Santhosh 
wrote:

> Hi,
>
> I am trying to install vagrant plugin "vagrant-libvirt". I have downloaded
> all the necessary .gem file in my local machine which does not have access
> to internet. I am facing the following error...
>
> # vagrant plugin install vagrant-libvirt-0.0.45.gem
>
> Installing the 'vagrant-libvirt-0.0.45.gem' plugin. This can take a few
> minutes...
>
> Vagrant failed to load a configured plugin source. This can be caused
> by a variety of issues including: transient connectivity issues, proxy
> filtering rejecting access to a configured plugin source, or a configured
> plugin source not responding correctly. Please review the error message
> below to help resolve the issue:
>
>   no such name (https://gems.hashicorp.com/specs.4.8.gz)
>
> Source: https://gems.hashicorp.com/
>
>
>
> Why it is trying to access internet when we are pointing it to local gem
> file ?? Is it possible to install vagrant plugin offline ? This is bottle
> neck for us, please let us know if offline installation is possible or not.
>
> Thanks in advance
>
> -Sahana
>
> --
> 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/4454c8d3-c52d-4ac1-8fb5-bdabf8b29428%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/CAHqq0ey0tupMRGPZXZWCwrHt7%2BWDgSao%2BAiERk%3DshPa14mZatA%40mail.gmail.com.

Re: [vagrant-up] feeding the host ssh port into the provisioner

[Alvaro Miranda Aguilera]

hello

2 things

1. you can set the port to something known

on one VM

config.vm.network :forwarded_port, guest: 22, host: 2291, id: "ssh"


on the second VM

config.vm.network :forwarded_port, guest: 22, host: 2292, id: "ssh"


and test


2. disable the insert ssh_key so you can connect with the insecure key



config.ssh.insert_key

=
false


then try to login with the insecure ssh key

https://github.com/hashicorp/vagrant/blob/master/keys/vagrant



Alvaro





On Fri, Oct 18, 2019 at 8:45 PM steve gibson  wrote:

> Hi,
>
> I'm am looking for a way to get the host port for the SSH port-forward and
> be able to write it in a file on the guest.
>
> My scenario is this:
> I have a multi-machine setup with 2 VMs (using vbox). Both machines need
> to be able to scp to each other. Since eth0 is on a private network, I
> cannot access one guest from the other. And because of the nature of my
> project, I cannot add a second network interface.
> So I am looking for a way to create a /root/.ssh/config file on each guest
> and define the peer guest with the port that is made available on the host.
> The IP would be the GW of the guest
>
> So how can I get VM1's ssh port when I am provisioning VM2 ?
>
> 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/077d5476-dff0-4db8-9d5e-029b9ef4a0d6%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/CAHqq0ey91tXZP7DP755Otkx_aNM_%3DNJnbPCex7wd6KPEhYC2rQ%40mail.gmail.com.

Re: [vagrant-up] Change DNS for provionned box

[Alvaro Miranda Aguilera]

are those the dns of your host machine?

have you tried with a provisioning script set the new dns ?

alvaro

On Mon, Oct 28, 2019 at 9:48 AM Jean-Marc Messina 
wrote:

> Hi
>
> I need to spawn a bunch of boxes with vagrant that would use my DNS
> servers. Currently, they seem to use a static list that is :
>
>- 4.2.2.1
>- 4.2.2.2
>
> I'm quite new to terraform and have, so far, failed to find how to change
> these.
>
> Any clue ?
>
> --
> 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/82b49a4e-aa2b-4592-b646-25eb4eda54b1%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/CAHqq0ewYnn_ma7R3hdFPRG5iCukQ3JbkUickEToc4w0A4YOc_Q%40mail.gmail.com.

Re: [vagrant-up] Vagrant ssh no longer working

[Alvaro Miranda Aguilera]

is this pure development?

if the VM gets into a inconsistent state, destroy/recreate is common
practice the VMs should be disponsable.

depening on the hypervisor you ae using, not sure if virtualbox or hyper-v
you should be able to login from the console

you may try to reload the vm, vagrant reload

however you should be able to login over the console and check the logs and
troubleshoot what is happening here

good luck

alvaro

On Fri, Oct 25, 2019 at 10:56 PM TB  wrote:

> Hello,
>
> I need help.  Recently, my chef server vagrant was working one day and the
> next it stopped working.  Everytime I run 'vagrant ssh' it said
> "ssh_exchange_identification: read: Connection reset by peer.' message.
> I've looked for this error message online, from other users suggesting to
> run vagrant halt, then vagrant up to bring it back, but it stills won't
> work.  Some suggested to check for enabling hyper-v and enabling vt-x, and
> it stills won't work.  I am thinking about to run vagrant destroy and bring
> back up again to its normal state with vagrant up, but afraid I might loose
> everything or how long it will take to get vagrant back to its normal
> working condition.
>
> Any suggestions/ideas to what caused this and how to resolve this?
>
>
> --
> 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/c8820066-5da0-4a1d-a75e-a24652e137e1%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/CAHqq0eyGwhO6dFGFg%2B%2Ba4Du%3DKMY-WWFvEB1OBSXyxATBdbJMeQ%40mail.gmail.com.

Re: [vagrant-up] Vagrant 2.2.6 on mac Os Catalina : Failed to start The Apache HTTP Server

[Alvaro Miranda Aguilera]

that is happening inside the VM.

so is not a vagrant issue at first sight

check the configuration file per error, seems line 7 is not good

Oct 28 03:43:18 homestead apachectl[3468]: AH00526: Syntax error on line 7
of /etc/apache2/sites-enabled/landingpage.local-ssl.conf:

alvaro

On Tue, Oct 29, 2019 at 1:21 AM Agus Mahendra B  wrote:

> macOS Catalina 10.15
> Vagrant 2.2.6 (installed via homestead)
>
>
> When I do "vagrant ssh" and "flip" ngix to appache, the process fails
> around this spot:
> nginx stopped
> Job for apache2.service failed because the control process exited with
> error code.
> See "systemctl status apache2.service" and "journalctl -xe" for details.
> apache started
>
>
> When I do "systemctl status apache2.service" showing like below:
>
> vagrant@homestead:~$ systemctl status apache2.service
> apache2.service - The Apache HTTP Server
> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor
> preset: enabled)
> Drop-In: /lib/systemd/system/apache2.service.d
> └─apache2-systemd.conf
> Active: failed (Result: exit-code) since Mon 2019-10-28 03:43:18 UTC; 26s
> ago
> Process: 3468 ExecStart=/usr/sbin/apachectl start (code=exited,
> status=1/FAILURE)
>
> Oct 28 03:43:18 homestead systemd[1]: Starting The Apache HTTP Server...
> Oct 28 03:43:18 homestead apachectl[3468]: AH00526: Syntax error on line 7
> of /etc/apache2/sites-enabled/landingpage.local-ssl.conf:
> Oct 28 03:43:18 homestead apachectl[3468]: DocumentRoot takes one
> argument, Root directory of the document tree
> Oct 28 03:43:18 homestead apachectl[3468]: Action 'start' failed.
> Oct 28 03:43:18 homestead apachectl[3468]: The Apache error log may have
> more information.
> Oct 28 03:43:18 homestead systemd[1]: apache2.service: Control process
> exited, code=exited status=1
> Oct 28 03:43:18 homestead systemd[1]: apache2.service: Failed with result
> 'exit-code'.
> Oct 28 03:43:18 homestead systemd[1]: Failed to start The Apache HTTP
> Server.
>
>
> Has anyone experienced the same problem as me?
>
> --
> 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/601e9b50-3409-4d6d-86f0-375ff7fcfdc8%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/CAHqq0exEruskiiuTUNvQnPuOJ4DMLR7Fy9-heNfPPvbT37X09w%40mail.gmail.com.

Re: [vagrant-up] Vagrant error for adding a box, bsdtar: Error opening archive: Unrecognized archive format

[Alvaro Miranda Aguilera]

one option is download was incomplete.

other option is the file is damaged

try to delete the file and try a new download

alvaro

On Fri, Nov 1, 2019 at 12:43 PM sarah shakeri 
wrote:

> Hi,
>
>
>
> Vagrant version is: 2.2.6
> The host system is: Ubuntu 18.04.3 LTS
>
>
> I am going to add a box in vagrant by
>
> vagrant box add juniper/vqfx10k-pfe vqfx10k-pfe.box
>
> but I get below error:
>
> ==> box: Box file was not detected as metadata. Adding it directly...
> ==> box: Adding box 'juniper/vqfx10k-pfe' (v0) for provider:
> box: Unpacking necessary files from: 
> file:///home/sshakeri/ron19_sr/lab/vqfx10k-vagrant/vagrant_boxes/vqfx10k-pfe.box
> The box failed to unpackage properly. Please verify that the box
> file you're trying to add is not corrupted and that enough disk space
> is available and then try again.
> The output from attempting to unpackage (if any):
>
> bsdtar: Error opening archive: Unrecognized archive format
>
> Do you know what can be the possible problem?
>
> --
> 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/0c59721d-4b50-4dcd-b5b7-713ddb4a26a4%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/CAHqq0ewkuE3HQWpHoJnsfBmP1W2pHUBmyo6CgnOM5SzUn%2BPn-A%40mail.gmail.com.

Re: [vagrant-up] Ping/Request OK in LAN, but KO via WAN

[Alvaro Miranda Aguilera]

you may be missing a router in this ip

whats the output of route print ?



On Fri, Nov 1, 2019 at 5:22 PM Namlu u  wrote:

> Hi !
>
> Summary:
> I have a virtual machine that hosts a website. The site is accessible
> anywhere in the local network, but neither to computers connected in VPN,
> nor in WAN interrogation with a correct port forwarding.
>
> Technically:
> - *Vagrant version*: 1.9.1
> - *Virtualbox version*: 5.2.34
> - *Host and virtual OS*: Debian 9
> - The website is the default installation of a nginx installed on the host
> (for diagnostics) and the virtual machine
>
> - Vagrantfile network configuration:
>
> config.vm.network "public_network", bridge: "enp0s25", ip: "192.168.1.201"
>
>
> - WAN forwarding port:
>
> 10080  >  192.168.1.100:80
> 20180  >  192.168.1.201:80
>
>
> Tests:
>
> *From raspberry in LAN (192.168.1.88)*
>
>
>- ping 192.168.1.100 *[host]*: *OK*
>   - ping 192.168.1.201*[vm] *   : *OK*
>   - curl 192.168.1.100 *[host]* : *OK*
>   - curl 192.168.1.201 *[vm] *   : *OK*
>   - curl mydomain:10080 *[host]* : *OK*
>   - curl mydomain:20180 *[vm]*   : *OK*
>
> *From my cellphone on VPN (192.168.1.52**)*
>
>- ping 192.168.1.100 *[host]*: *OK*
>- ping 192.168.1.201*[vm] *   : *KO*
>- curl 192.168.1.100 *[host]* : *OK*
>- curl 192.168.1.201 *[vm] *   : *KO*
>- curl mydomain:10080 *[host]* : *OK*
>- curl mydomain:20180 *[vm]*   : *KO*
>
> *From my cellphone off VPN (192.168.0.3**)*
>
>
>- curl mydomain:10080 *[host]* : *OK*
>   - curl mydomain:20180 *[vm]*   : *KO*
>
>
> Conclusion:
> I concluded it's my configuration of Vagrant and / or Virtualbox that is
> problematic. Do you have an idea of ​​what can happen?
> Thanks for your help !
>
> More data:
> - *Vagrant version* 1.9.1
> - *Virtualbox version* 5.2.34
> - *Host and virtual OS* Debian 9
> - *ifconfig on host*
>
> enp0s25: flags=4163  mtu 1500
> inet 192.168.1.100  netmask 255.255.255.0  broadcast 192.168.1.255
> ether 00:15:17:e6:94:bc  txqueuelen 1000  (Ethernet)
> RX packets 10351311  bytes 12044849276 (11.2 GiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 8569810  bytes 669605531 (638.5 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 20  memory 0xc2b0-c2b2
>
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1  (Boucle locale)
> RX packets 446809  bytes 51801204 (49.4 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 446809  bytes 51801204 (49.4 MiB)eth0:
> flags=4163  mtu 1500
> inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
> inet6 fe80::a00:27ff:fe8d:c04d  prefixlen 64  scopeid 0x20
> ether 08:00:27:8d:c0:4d  txqueuelen 1000  (Ethernet)
> RX packets 11678  bytes 15457601 (14.7 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 5981  bytes 423088 (413.1 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
>
> - *ifconfig on virtual machine*
>
> eth0: flags=4163  mtu 1500
> inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
> inet6 fe80::a00:27ff:fe8d:c04d  prefixlen 64  scopeid 0x20
> ether 08:00:27:8d:c0:4d  txqueuelen 1000  (Ethernet)
> RX packets 11678  bytes 15457601 (14.7 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 5981  bytes 423088 (413.1 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> eth1: flags=4163  mtu 1500
> inet 192.168.1.203  netmask 255.255.255.0  broadcast 192.168.1.255
> inet6 2a01:e35:2f4d:7aa0:a00:27ff:fe91:41e5  prefixlen 64  scopeid
> 0x0
> inet6 fe80::a00:27ff:fe91:41e5  prefixlen 64  scopeid 0x20
> ether 08:00:27:91:41:e5  txqueuelen 1000  (Ethernet)
> RX packets 110921  bytes 149988100 (143.0 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 83255  bytes 8211893 (7.8 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1  (Local Loopback)
> RX packets 8  bytes 540 (540.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 8  bytes 540 (540.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> --
> 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
> ---
> 

Re: [vagrant-up] Create virtual interfaces for create isolated envs

[Alvaro Miranda Aguilera]

hello

on virtualbox the VM will have nat, and from there should be access any VM
that your host can access.

As each net VM will be on his own switch if the nics are different, but all
these switch are available to the host, every machine should be able to
reach any machine over the NAT interface.

is not clear from the diagram how you want to do it. can you elaborate a
bit more? maybe a diagram will help.

then, second question is why the projects need to be isolated?

are going to be using same ip segmentation?




On Sat, Nov 23, 2019 at 5:40 PM Fabio Pezzini  wrote:

> I'm trying to create isolated environments containing both Vm (virtualbox)
> and containers (docker). Then using virtualbox and docker.
> What I'm trying to achieve are closed networks where ONLY the machines in
> the given project can talk.
> The only way I could think of is by creating interfaces with a given
> gateway assigned to the virtual interface on the host machine and assigning
> this interface to all the guests I want to enclose in the subnet.
> I tried creating virtual namespaces but they can't talk (especially
> between container and vm). How can I do?
>
> --
> 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/dd4d7b76-6ebe-4730-a7e0-935fcd96990d%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/CAHqq0eySrje%2Ba73VCoQj446MGC%2BuZpQ%3DK-zdxGA8Q3FUXKpYgQ%40mail.gmail.com.

Re: [vagrant-up] Why does vagrant global-status not work but local status does?

[Alvaro Miranda Aguilera]

not sure

worth to try run


vagrant global-status --prune

and share the output of

vagrant global-status
 vagrant destroy {id} --debug

share the verbose output as a file

thanks
alvaro

On Thu, Nov 7, 2019 at 5:13 PM Andy Rose  wrote:

> I actually added this as a Stackoverflow question too.. FYI
>
>
> https://stackoverflow.com/questions/58752300/why-does-vagrant-global-status-not-work-but-local-status-does
>
> Context
>
>
> Vagrant 2.2.5
>
>
> Windows 10, everything was working fine. A different issue caused my disk
> space to be used up, I tried to vagrant destroy {id} and the destroy
> failed due to not enough disk space.
>
> After that, running vagrant global-status says I have no active
> environments.
>
>
>
> Symptoms
>
> vagrant global-status says I have no environments.
>
>
> If I open VirtualBox directly it can see all my Vagrant VMs listed.
>
>
> If I compare the IDs for the VMs from VBox to the IDs in the .vagrant
> folders they match.
>
>
> And finally, if I run vagrant status from the local project path,
> everything works fine. I can up, halt, destroy, I can ssh into them fine.
>
> The only thing that doesn't work is global-status.
>
>
> Why?
>
>
>
> Thanks all!
>
>
> Andy
>
> --
> 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/ebd649d2-5252-4ea3-af2c-62b65b272e45%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/CAHqq0ewfFCruAb%2BYKpFRxE80CG9g35L07b5YJCWjTWatEX6NvA%40mail.gmail.com.

Re: [vagrant-up] Powershell error

[Alvaro Miranda Aguilera]

hi there

whats your host os ?

if windows, is fully upto date ?

have you installed powershell 3 or higher ?

do you have any plugin installed?


On Mon, Nov 11, 2019 at 5:04 AM T  wrote:

> Vagrant failed to initialize at a very early stage:
>
> The version of powershell currently installed on this host is less than
> the required minimum version. Please upgrade the installed version of
> powershell to the minimum required version and run the command again.
>
>   Installed version: N/A
>   Minimum required version: 3
>
> --
> 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/ad460583-1faf-4735-8a38-44dde7dfbc5f%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/CAHqq0ezGeS0W3keC1%2BuQ_VcuP1pYTsh6aWxvbeYRVrhOYnDHhA%40mail.gmail.com.

Re: [vagrant-up] Re: vagrant complains about VMware license when importing a vbox .box file

[Alvaro Miranda Aguilera]

check if your installation have any license and remove it
vagrant plugin list
vagrant plugin uninstall vagrant-vmware-

share output of vagrant plugin list and the packer code you are using.

you can add the provider to force virtualbox like this:
https://www.packer.io/docs/builders/vagrant.html#example


Thanks
alvaro.

On Mon, Nov 11, 2019 at 7:58 PM voidSurfr  wrote:

> also, just removed all the VMware bits and Vagrant is still complaining.
>
> Is the vagrant check to simply see if fusion is installed? Then, if no
> license: error?
>
>
>
> On Friday, November 8, 2019 at 5:36:14 PM UTC-8, voidSurfr wrote:
>>
>> Hey guys,
>>
>> Building an image with packer for vagrant box consumption. I have
>> definition in the packer build for vmware-fusion and vbox. build-time
>> parameter is* -only=virtualbox *though.
>>
>> When I go to import the vbox .box file Vagrant still requires the licence
>> for vmware.
>>
>> packer build -color=false -force -only=virtualbox-iso centos-75-cis.json
>> ...
>> Build 'virtualbox-iso' finished.
>>
>> ==> Builds finished. The artifacts of successful builds are:
>> --> virtualbox-iso: 'virtualbox' provider box:
>> /Users/me/vms/vagrant/boxes/centos/centos-7.7-cis.virtualbox.box
>> + break
>> + echo -e 'Adding CentOS 7 / CIS to the local registry...'
>> Adding CentOS 7 / CIS to the local registry...
>> + sleep 5
>> + vagrant box add --force centos-cis
>> /Users/me/vms/vagrant/boxes/centos/centos-7.7-cis.virtualbox.box
>> A valid license is required to run the Vagrant VMware
>> provider. Please visit http://www.vagrantup.com to purchase
>> a license. Once you purchase a license, you can install it
>> using `vagrant plugin license`.
>>
>> Is there any way through this? I don't use these tools much any more so
>> the packer/vagrant muscles have gone somewhat weak; any help would be
>> greatly appreciated.
>>
> --
> 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/74b457d4-3b6f-48b2-ad2c-fce0524b1293%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/CAHqq0ez_PM0iqJb-jrJ3dWabdbmoqpqS-c2X9bqoY0Lqn8WXZg%40mail.gmail.com.