hello
https://github.com/hashicorp/vagrant-installers
Alvaro
On Fri, Oct 4, 2019 at 3:11 AM is a wrote:
> Hi,
>
> Could anyone tell me where is the source code of vagrant.exe on Windows? I
> noticed Exeinfo PE reports it as unknown EXE and I'm curious how it's
> implemented. I can't find it
if you are using packer with vagrant provider, is expected the box will be
ssh and ready to use
usually will have a vagrant user with the vagrant known ssh
so vagrant can ssh.
on first boot, vagrant will insert a new ssh cred.
you can see what ssh will be used with
vagrant ssh-config
you
can you share both Vagrantfiles ?
On Thu, Sep 26, 2019 at 9:12 PM Carlos Albornoz
wrote:
> Hi, I have installed vagrant-2.2.5-2 + libvirt as provider on Archlinux,
> when up a VM the nat network set correctly the IP, but when up a second VM,
> dhcp lease the same IP, with the obvious network
is your machine on a Windows domain ?
On Tue, Sep 24, 2019 at 5:58 PM bob torroid wrote:
> Took almost 20 minutes. This was an install of 2.2.5 on top of an earlier
> version. Win10 64bit, has to run McAfee, several large USB drives. Any
> insights from those familiar with the installer?
>
>
Hello
If you could put in a github repo the project ready to use, and you share
instructions will be easier to see what you would like to do.
Thanks
alvaro.
On Wed, Sep 18, 2019 at 7:43 PM Jayjeet Chakraborty <
jayjeetchakrabort...@gmail.com> wrote:
> I have a vagrant VM provisioned with
hello
Virtualbox will create a virtual switch
HOST -> Switch <-VM
This is how the networking works
if you add more VMS and/or more IPs they will be connected to the virtual
switch
<- VM with ip 192.168.33.10
HOST -> Switch <- VM with ip 192.168.33.11
hello there
i think, it will be better if you build your own box ready to use.
will be more simple and quicker for developers to do vagrant up
alvaro.
On Fri, Sep 6, 2019 at 8:19 PM Sorcerer Stone
wrote:
> Hello All,
> My Linux development environment is Vagrant + VirtualBox on top of a
docker machine have his own way to create a virtualbox VM for docker
you are creating a VM with vagrant, that is fine
but i believe will be separate to the VM that docker-machine will create
how are you creating the VM with docker machine?
or
why want to create a vm with vagrant and then use
hello
rsync in vagrant connect over ssh, no need to have rsync daemon.
alvaro
On Wed, Aug 14, 2019 at 3:46 AM Andrew Pennebaker <
andrew.penneba...@gmail.com> wrote:
> Does Vagrant's rsync provisioner require the guest to run rsync in daemon
> mode, or is it enough to run a raw rsync client?
try adding this
config.vm.provider :virtualbox do |vb|
vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
end
On Thu, Aug 8, 2019 at 9:49 PM Devils Kiddo wrote:
>
> I am on Windows 10, using a centos 7 box, for DNS tools, mostly. I need
> them for domains and DNS stuff.
0.0.0.0:28017 NOTE05:0 LISTENING
> TCP0.0.0.0:35729 NOTE05:0 LISTENING
>
>
> Em sábado, 20 de julho de 2019 13:30:53 UTC-3, Alvaro Miranda Aguilera
> escreveu:
>>
>> whats the output of netstat -ano from windows ?
>>
something either in the project you are using like an script is configuring
the vm.
inside the VM, docker has been installed, thats why you see docker0.
you will have to search your scripts to see if there is anything creating
the bridge.
you can try like
# this is to delete the VM
vagrant
can you try to reproduce with a different box?
if you are able to reproduce, please open a issue on github with the steps
thanks
alvaro
On Fri, Jul 26, 2019 at 5:00 PM Mohammad Amin wrote:
> I'm using laravel homestead on windows with hyper-v
> Whenever I use 'vagrant up' or 'vagrant reload
seems these boxes are more up to date
https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/
On Sun, Jul 28, 2019 at 9:49 PM g p wrote:
> I cannot get a minimal windows box working using the official windows box.
>
> I have tried the following vagrant files:
>
>
answer is yes, and is perpetual for the versions you are buying.
Workstation 15 and Fusion 11 as today.
for any vagrant vmware plugin, please email support @ hashicorp.com
thanks
On Fri, Jul 26, 2019 at 4:34 AM venkatesh javvaji
wrote:
> Can we use same Vagrant license for both windows
whats the output of netstat -ano from windows ?
check around those ports you are interested and share the output here
On Fri, Jul 5, 2019 at 8:37 PM mcolla wrote:
> Hi everyone,
>
> My default SO is Win10. I have a VM with CentOs, and MongoDB inside. How
> access MongoDB?
> I want access
hello
if you want virtualbox boxes you will need to build boxes where you can run
virtualbox.
there is no service ti build boxes automatically, so you will have to do
some work
you can automate much of the process with packer (packer.io)
alvaro
On Sat, Jul 6, 2019 at 1:21 AM Jason Hsu
the issue is on the service only listening to 127.0.0.1:1636
you will have to update to bind to all interfaces. check the documentation
of the product
On Sat, Jul 20, 2019 at 10:49 AM Surendra Singh Khatana <
surensinghkhat...@gmail.com> wrote:
> Hi,
> I have installed a packaged software (Gluu
hello is better if you try to build your own box with packer (packer.io)
https://github.com/luciusbono/Packer-Windows10
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines
and enabling network interfaces...
> ==> default: Mounting shared folders...
> default: /var/www => F:/october-demo
> ==> default: Machine already provisioned. Run `vagrant provision` or use
> the `--provision`
> ==> default: flag to force provisioning.
hello
Are 2 separate things here.
Templates and running VMs.
Templates or vagrant boxes is from where a running VM will be created.
vagrant box list
will show vagrant boxes or templates.
A total separate thing is running VMs.
vagrant global-status
this will display the running VMs and
hello
Can you share md5 sum and sha256 sum of the installer and that particular
file please
also let me know the version.
I will confirm if the the signatures are the same, run some AV test and
will try to report to AVAST
We have had some false positives on the past.
Thanks for sharing this
hello
you can disable the default shared folder..
https://www.vagrantup.com/docs/synced-folders/basic_usage.html#disabling
alvaro
On Wed, Jun 26, 2019 at 11:27 AM Aleksandr Dorogush
wrote:
>
> Host: mac os 10.14.5
> virtualbox 6.0.8
> virtualbox extension pack 6.0.8
> vagrant 2.2.5
>
>
hello
you need to install this package
https://releases.hashicorp.com/vagrant/2.2.5/vagrant_2.2.5_x86_64.deb
that will install vagrant
On Tue, Jun 25, 2019 at 11:07 PM Ajay Kumar
wrote:
>
>
> Hello,
>
> I am trying to install Vagrant 2.2.4 in Ubuntu 18.04 machine but getting
> this below
if you host already have virtualbox, why not running vagrant there ?
--
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.
hello
whats the output of
netstat -anp | grep 4200
in the guest vm ?
On Thu, Jun 13, 2019 at 10:09 PM Zac Harvey
wrote:
> I have the following Vagrantfile:
>
> Vagrant.configure("2") do |config|
> config.vm.box = "bento/ubuntu-18.04"
> config.vm.network "forwarded_port",
hello
you can run 32bit guest inside virtualbox
if your guest is 64bit you may have issues.
if you host already have virtualbox, why not running vagrant there ?
thanks
alvaro
On Mon, Jun 17, 2019 at 9:40 AM Mohammed Rafiq
wrote:
> I have a windows 10 OS machine, I have installed Oracle
hello
you can repeat the network configuration multiple times
ie
config.vm.network "private_network", ip: "192.168.50.4"
config.vm.network "private_network", ip: "192.168.51.4"
config.vm.network "private_network", ip: "192.168.52.4"
On Thu, Jun 13, 2019 at 11:32 AM Nilashish Chakraborty <
com> wrote:
> Xen Project is the new name of Xen.
> Why Xen box not existed?
> I like to have a Vagrant Xen box. I mean is that I like to have a Xen
> hypervisor box.
>
>
> On Saturday, June 8, 2019, 3:27:40 PM GMT+4:30, Alvaro Miranda Aguilera <
> kiki...@gmail.c
> On Friday, June 7, 2019, 2:02:41 PM GMT+4:30, Alvaro Miranda Aguilera <
> kiki...@gmail.com> wrote:
>
>
> did you test any box ?
>
> they fail to boot?
>
> any error message?
>
> On Fri, Jun 7, 2019 at 7:03 AM 'Jason Long' via Vagrant <
> vagrant-u
try
vagrant share --debug
and share the verbose log, ideally as an attached text or gist (
gist.github.com)
On Fri, Jun 7, 2019 at 11:14 AM wahsidin Tjandra
wrote:
> default: Detecting network information for machine...
> default: Local machine address: 127.0.0.1
> default:
>
did you test any box ?
they fail to boot?
any error message?
On Fri, Jun 7, 2019 at 7:03 AM 'Jason Long' via Vagrant <
vagrant-up@googlegroups.com> wrote:
> Thanks, but I meant was not XenServer. I meant was Xen Project.
>
> On Friday, June 7, 2019, 1:11:01 AM GMT+4:30, Brian Cain <
>
even if I disable the firewall.
>
> Thanks for looking at my question.
>
>
> On Tuesday, June 4, 2019 at 12:24:56 AM UTC-7, Alvaro Miranda Aguilera
> wrote:
>>
>> hello
>>
>> on the postgresql node whats the output of
>>
>> sudo netstat -anp
if you want to copy a file from host to vm, you can use a file provision
https://www.vagrantup.com/docs/provisioning/file.html
On Fri, May 31, 2019 at 3:18 PM Zeus_Dev wrote:
> Hello everyone :)
>
> Im having a vagrantfile with a ubuntu (ubuntu/xenial64) and installing PHP
> 7.3 on the VM in
hello
vagrant up will configure a VM based on Vagrantfile and provisioning
if you want to have a new base box that include more than just the base OS
have a look at packer.io
it will create a box and you can run the same scripts
https://packer.io/docs/builders/vagrant.html
On Tue, May 28,
hello
whats the specific question?
- how to install python pip?
sudo apt-get update
sudo apt-get install -y python-pip
alvaro
On Wed, May 29, 2019 at 12:48 AM 'Karen Goh' via Vagrant <
vagrant-up@googlegroups.com> wrote:
> Hi,
>
> This is obviously very simple for some people but I am just
hello
you can do multi machine on same vagrant file and use private_network to
allow intra vm networking
example
# -*- mode: ruby -*-
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
#
1, 2019 at 2:45:24 PM UTC-4, Alvaro Miranda Aguilera
> wrote:
>>
>> error seems to say some issues on vagrantfile
>>
>> have you check your vagratfile is properly done for host manager version
>> installed ?
>>
>> On Tue, May 21, 2019 at 1:16 PM Sh
hello
please email support at hashicorp.com
for Fusion 11 the best is you use a new plugin called vagrant-vmware-desktop
i did check your email and seems you have a license for Fusion 10, and an
upgrade is needed for Fusion 11 in your case.
if you email support I can generate a discount code
vagrant to be able to create vmware vms, need a plugin
when plugin is installed the default provider will be virtualbox
https://www.vagrantup.com/vmware/index.html
alvaro
--
This mailing list is governed under the HashiCorp Community Guidelines -
error seems to say some issues on vagrantfile
have you check your vagratfile is properly done for host manager version
installed ?
On Tue, May 21, 2019 at 1:16 PM Shanthamurthy Hanumantharayappa <
shamuh2...@gmail.com> wrote:
> Hi,
>
> Vagrant up is shutting down before Running provisioner:
what tools those developers with crosstooling use?
maybe not vagrant.
On Sat, May 11, 2019 at 11:15 PM Dennis Chang
wrote:
> To answer your question about my goals (it's more like a wish, I can't see
> how I have the time to do all of this):
>
> Basically, Linux from scratch, from Slack 3.2,
hello
few ideas first.
vagrant is for development work, and development work only should be the
focus.
way vagrant have been develop,
for non-development work, are other tools more suitable for the task, say
terraform or any other tool that the goal is provision infrastructure to be
run and
whats the problem on using docker for all your needs?
On Fri, May 10, 2019 at 3:58 PM Dennis Chang wrote:
> Hi all,
>
> This is part question and part request for comment.
>
> I've become more familiar with Docker and I'd like Vagrant to be patterned
> similarly.
>
> E.g.
>
> docker images
>
do you have a Vagrantfile on that directory?
whats the context of the 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
set the VAGRANT_HOME var to a shared path, will the VM be also
> created there or do I have to set that in the VirtualBox environment
> explicitly?
>
> Thank you,
>
> Pp
>
> On Thursday, April 25, 2019 at 11:41:58 AM UTC-4, Alvaro Miranda Aguilera
> wrote:
>>
>>
hello
not sure I do understand where is the problem, so let me address 2
scenarios.
You want to have a VM available over the network, why you creating one, and
share it over the network, ppl can access as user/pass ip ?
otherwise, you want to have local users using the same template and not
hello
check os manual documentation, you may need to install the package, enable
the service, start the service.
On Sat, Apr 20, 2019 at 8:51 AM hack3rcon via Vagrant <
vagrant-up@googlegroups.com> wrote:
> Hello.
> I installed Vagrant on Debian 9 x86_64 and added a "ubuntu/trusty64" box.
> I
5:08 UTC+3, Alvaro Miranda Aguilera wrote:
>>
>> hello
>> when you run sudo, it ask for the user password
>>
>> the vagrant file seems to be creating a user, just not sure why you need
>> that in that way.
>>
>> whats the requirement that the user need to b
virtuabox to be able to create a 64 bit guest, requires access to hw that
is not available inside a vm generally.
vmware can emulate the hw, and you could do vm inside vm in vmware, however
what you want to do here?
if you can create vm on xen, why you need a vm inside vm ?
On Wed, Apr 17,
hello
when you run sudo, it ask for the user password
the vagrant file seems to be creating a user, just not sure why you need
that in that way.
whats the requirement that the user need to be sorin and not vagrant?
i would suggest to create a new box right to use, it helps in the long run
hello
got a question:
say you get this up and running, how you plan to use it from vagrant?
being docker available over the network, if you can spin the emulator, and
expose the docker daemon, then you can just use it.
Not sure how vagrant fits here on this particular scenario.
if running
hello this hasn't changed much.
you can use packer to build boxes.
Something new is that packer now can build from an existing vagrant box, so
saves time as will be using a local base box.
https://packer.io/docs/builders/vagrant.html
There is an example too.
Alvaro.
On Fri, Apr 12, 2019 at
hello
each plugin have instructions on how to install, basically
vagrant plugin install
what plugin you really need for work?
i wouldn't suggest bypass security, and will suggest engage security. if
the veto a plugin due origin, then i am afraid is not much we can do to
help, it seems
hello
vagrant cloud moved to app.vagrantup.com
so seems something is cached in your machine.
try this
- upgrade to latest version of vagrant
- delete .vagrant.d/boxes
try to add the box as
vagrant box add hashicorp/precise64
Thanks
Alvaro
On Mon, Apr 8, 2019 at 8:17 PM ashkarthik
wrote:
hello
if you share your vagrantfile we can have a look
in the old days you could disable shared folder that required ssh and that
was the only component that required vagrant to ssh
now, if vagrant doesn't do what you require, have you tried different
alternatives?
vagrant as far as I know
Hi there
- does your virtualbox works? can you create and boot a vm without vagrant?
- have you tried a different box?
mkdir p64
cd p64
vagrant init -m hashicorp/precise64
vagrant up
if this fails, share
vagrant version
vagrant plugin list
Vagrantfile and the output of
vagrant destroy
vagrant
Hello
Say you want to start a vm, centos/7
When you do vagrant box add centos/7 it will download a base box (like a
template)
then you can create a vm like this
mkdir centos7
cd centos7
vagrant init -m centos/7
if you do vagrant status it will show a default box using centos/7
don't change
protocol as well.
>
> I just need to know how to tell Vagrant to disable SSL and use TLS instead.
>
> Thanks!
>
> On Thursday, March 28, 2019 at 10:36:42 AM UTC-4, Alvaro Miranda Aguilera
> wrote:
>>
>> Hello
>>
>> Using this proxy and a different project
Hello
Using this proxy and a different project does work?
mkdir p64
cd p64
vagrant init -m hashicorp/precise64
vagrant up
Does this work?
How do you specify the proxy?
Thanks
Alvaro.
--
This mailing list is governed under the HashiCorp Community Guidelines -
hello
what is the question around the error message?
is basically saying is trying to read an iso and the iso is not there
As there is no more support information is not much how to help.
Whats the vagrant file you are using?
have you tried different box, different vagrant?
did you try
hello.
when the vagrant up command fails, check
the output of . vagrant ssh-config
vs whats in the the virtualbox , VM - > settings, network, port forwarding.
does match ?
On Thu, Mar 21, 2019 at 3:07 PM wrote:
> Recently Vagrant ssh stopped working and I can't figure out why. It's
>
hello.
make your scripts idempotent.
just add those lines if you need them
ie
config.vm.provision "shell", inline: 'grep P4CONFIG /home/vagrant/.bashrc
|| echo "export P4CONFIG=/vagrant/repos/.p4config" >> /home/vagrant/.bashrc'
Thanks
Alvaro
On Sat, Mar 23, 2019 at 12:20 AM Jason Yu
Hello.
After the command fail, and you get the VMX file. ie:
C:\\Users\\Aaron
Kulbe\\Code\\sandbox\\.vagrant\\machines\\default\\vmware_desktop\\561078a5-7c47-440c-a4e8-d7d9865c96d4\\centos-7-1-1.x86_64.vmx"
Try to open it, and see what the GUI says.
As you are on the vmware plugin, you could
hello
error message says there is already some files on that path:
VBoxManage: error: Appliance write failed
VBoxManage: error: RTVfsFsStrmAdd failed for 'box.ovf' (VERR_ALREADY_EXISTS)
Can you try to delete "/Users/anshulmittal/.vagrant.d/tmp/*" and try again?
?
Alvaro
On Mon, Mar 25, 2019
hello.
Whats your host OS ?
is Hyper-V installed and enabled?
Can you create VMs?
Have you tried on a different host?
run :
vagrant destroy
vagrant up --debug
and share the full log.
Alvaro.
--
This mailing list is governed under the HashiCorp Community Guidelines -
hello
if you share what commands you run
what errors you see
will be easier to help
As you are using someone else repo, I will suggest open an issue with them
in case they can help you.
Alvaro.
On Sat, Mar 16, 2019 at 11:38 PM wrote:
> Hi everyone,
>
> Need some help, if anyone can offer.
>
i would suggest open an issue on the plugin for ovirt, perhaps they can
help you.
Alvaro.
On Tue, Mar 5, 2019 at 3:58 AM Jeremy Tourville
wrote:
> I am trying to start up a vm by running vagrant up. The process fails
> quickly with the following output. Can anyone give some suggestions on
hello
you need to use the vagrant plugin names.
$ vagrant plugin install vagrant-omnibus
On Tue, Mar 5, 2019 at 10:50 AM Ingo Plath wrote:
> I got a new PC with Windows 10 and installed vagrant 2.2.4
>
> We use the omnibus plugin in our vagrant boxes/files so I tried to install
> the vagrant
Hello
The best is you create your own base box that is fit for what you need.
As you are following a guide and is not working, there is not much I can
say on why is failing.
There are a lot of moving parts, and is quicker just build your own box.
Have a look at packer is a tool that build VMs
hello
how you are doing this operation?
what you have tried?
what happens?
have you check the snapshot page?
https://www.vagrantup.com/docs/cli/snapshot.html
Alvaro
On Sun, Jan 20, 2019 at 12:24 PM Ross Elliot wrote:
> I'd like to reload my box without saving the current state. I'd like
what link you are using?
have you tried from a different browser?
different network?
different computer?
Alvaro
On Tue, Jan 22, 2019 at 8:29 PM wrote:
> Cannot download Vagrant 64 bit for windows what should I do? It downloads
> all the way but does not finish. I have tried restarting my
its a warning only
you can ignore
Alvaro
On Wed, Jan 23, 2019 at 3:07 AM Ross Elliot wrote:
> Ubuntu 18.04 box.
> Vagrant 2.2.3
> Virtualbox: 6.0.2
> Virtualbox Extension Pack 6.0.2
>
> Output during vagrant up
>
> default: Checking for guest additions in VM...
> default: The guest
you can use the vagrant way, which i a bit extreme
vagrant destroy
vagrant up
or you can try over the console/ssh as other user, not sure what box you
use, so may or may not work
root/root
root/ubuntu
Alvaro
On Sun, Jan 20, 2019 at 11:09 AM Ross Elliot wrote:
> I have a vagrant box running
Hello
why you expect this to work? seems .name is not valid in machine
you already know the name of the box, "test-web"
why not use that?
also, you could use normal shell script to run the command in the VM and if
there is any output, will be printed on the console.
Alvaro.
On Wed, Jan 16,
Hello.
private_network will create a interface without access to the real network.
If you want to create a interface that have access to the real network,
then public_network is what you may need.
You can find more information here:
https://www.vagrantup.com/docs/networking/
Alvaro.
On Wed,
Hello
Thanks for reporting this.
We are reviewing the documentation, and seems the documentation could get
an update.
can you test as:
Vagrant.configure("2") do |config|
config.vm.provider "docker" do |d|
d.force_host_vm = true
d.build_dir = "."
end
end
Thanks
Alvaro
On Fri, Jan 11,
solved the problem completely!
>
> Now on to the next problem! :D
>
> Best regards,
> Thomas Qvidahl
>
> mandag 7. januar 2019 22.17.04 UTC+1 skrev Alvaro Miranda Aguilera
> følgende:
>>
>> hello
>>
>> you have a config in the node repo, may be that is wh
hello
you have a config in the node repo, may be that is what causing the
incremental issue
can you replace
config.vm.network "public_network", bridge: "eno2"
with
node.vm.network "public_network", bridge: "eno2"
for the ip part
does eno2 is a wired card ? if yes, does the dhcp have any
So, sometimes webservers or some apps need tome info from the filesystem
that shared folder doesn't have.
This cause issues on things like you update software on the dev machine
over a IDE but the website on the VM doesn't show the updates.
This is not a vagrant issue.
vagrant is a wrapper
say i want to be able to reproduce this
can you share the full sequence of commands and files i need to be able to
get the same as you?
alvaro
On Fri, Dec 21, 2018 at 5:02 AM Min wrote:
> I'm working with:
> - Windows 10 Home
> - Virtualbox 6.0 for windows
> - vagrant for windows 64 bit
>
>
this command:
vagrant up && export BABEL_ENV=default && node server.js
is the same as
vagrant up
export BABEL_ENV=default
node server.js
you sure thart will work?
you want to run that in your windows shell ?
error here:
'export' is not recognized as an internal or external command,
so far,
hello host only is.. vm to host only
you need a private network to vm to vm can talk
like this:
https://github.com/chavo1/multi-web/blob/master/Vagrantfile
On Tue, Dec 11, 2018 at 11:33 AM Alceu Rodrigues de Freitas Junior <
alceu.freitas...@gmail.com> wrote:
> Hello there,
>
> I'm new to this
hello
whats your host os and guest os ?
please share a sample vagrantfile, but make sure to remove any password
what you neeed to do that needs synced folder?
On Wed, Dec 12, 2018 at 8:49 AM Robin wrote:
> Hi I new the vagrant so please forgive my limited experience
>
> I am trying to set
hello
in the logs is not the part of the port fwd
it seems the winrm communicator expect the port 5985 for this.
can you open an issue in github? include the full log of vagrantup please
https://github.com/hashicorp/vagrant/issues
On Thu, Dec 13, 2018 at 7:28 PM mwinfie wrote:
> Port 5985
run other app, like xeyes to confirm all works
try this:
https://github.com/kikitux/vagrant-xeyes
On Thu, Dec 13, 2018 at 2:48 PM F.N wrote:
>
>
> I've prepaired an android development environment using apache cordova
> inside a vagrant box with ubuntu 16.04 by following mainly this
>
vagrant destroy and up are the best way to have clean environments
On Thu, Dec 6, 2018 at 6:54 PM wrote:
> I moved the vagrantfile folder (vagrant init) from e:/ to c:/ in windows.
> Now 'vagrant snapshot restore XXX' is throwring
>
> Stderr: VBoxManage.exe: error: RawFile#0 failed to create
é., 5 dic. 2018 a las 21:03, Alvaro Miranda Aguilera (<
> kiki...@gmail.com>) escribió:
>
>> hello
>>
>> Vagrant plugin is for VMWare desktop , Fusion and Workstation.
>>
>> https://www.vagrantup.com/vmware/index.html#buy-now
>>
>> For ESXi, ar
hello
the error is telling you tat that IP already exists.
comment out config.vm.network "private_network", ip: "10.2.2.2"
vagrant probabl does that for you already
if Virtualbox is using the network 10.2.2.x
then try a different network for your private_network
On Mon, Dec 3, 2018 at 12:07
hello
If you disable the AV/Firewall it works?
If yes, then is matter of finding what exclusion works.
you could exclude by network
you use http:/localhost: ?
then try to exclude localhost and 127.0.0.1 for all ports
On Sat, Dec 1, 2018 at 1:51 PM Jonas Petrikas wrote:
> Hello,
>
> I hope
hello
Vagrant plugin is for VMWare desktop , Fusion and Workstation.
https://www.vagrantup.com/vmware/index.html#buy-now
For ESXi, are some community plugin, you should be able to test and see
what works for you.
Take note that i think the plugins for vCenter work, I personally haven't
tested
need to be available in the path.
any directory that is in the PATH.
On Thu, Nov 29, 2018 at 2:18 PM Mark Sheppard
wrote:
> Hi Everyone,
> I am trying to run vagrant share on my windows 10 machine, I am getting
> the following information coming up when running vagrant share
>
>
hello
not enough information.
if your machines are having same hostname and that is causing this, then my
sugestion will be use different names.
or setup a non prod setup. ie centos or spacewalk for what you need,
On Thu, Nov 29, 2018 at 7:43 PM Amir Aziz wrote:
> Hello All,
>
> I have been
hello
what ip or url you type in the browser ?
On Tue, Nov 27, 2018 at 10:28 PM John S wrote:
> I changed from forwarded port to a private network, then ran vagrant
> reload but my browser keeps redirecting back to localhost and failing
>
> I can't seem to find anything on why this is
hello there
i am not sure i can understand what you need help with.
let ask few questions.
what you have built so far? - share vagrant file
what do you see? - share an screenshot
if you also share what you want to happen, and describe what is happening
will help.
As is today, i may understand
hello
when you add a vagrant box, it will add it to:
~/.vagrant.d/boxes
when you include files in the box they get added in the compressed file of
the box.
think on the template vm on disk and other files.
When you do vagrant init, you are just creating a new Vagrantfile, that
tells the local
Hello Alex!
Thanks for sharing that.
Ok, so basically your folders are not mounted.
Vagrant does the share folders as part of the vagrant up.
Each time you do vagrant up to start the VM
or vagrant reload to reboot the VM, vagrant will mount the files.
So make sure you are not operating the
not sure what you want to do
but as is, seems it will only do the test nagios server
On Fri, Nov 23, 2018 at 2:57 PM rhys.james.campbell via Vagrant <
vagrant-up@googlegroups.com> wrote:
> My full Vagrant file is as below. I've since "fixed" this by removing the
> increment and adding
the path seems correct
make sure you are in the vm
whats the output of
df -Ph
ls -al /examples/files
?
On Sat, Nov 24, 2018 at 5:51 PM wrote:
> Hi All,
>
> I have installed vagrant on windows 7 and downloaded repo from
> https://github.com/bitfield/puppet-beginners-guide-3.git (extracted
Hello
If you share the full Vagrantfile I can have a look
but this works:
*==> default: Forwarding ports...*
default: 80 (guest) => 8080 (host) (adapter 1)
default: 80 (guest) => 8081 (host) (adapter 1)
default: 22 (guest) => 2203 (host) (adapter 1)
*==> default: Booting VM...*
101 - 200 of 2200 matches
Mail list logo
