vagrant

问题 Whats a bulletproof way to determine if I am running inside a vagrant machine? Guest OS is Debian Linux, though if there are indicators per-os that would be great to have documented as well. 回答1: AFAIK, there isn't a way outside of your own customizations. One idea that comes to mind is to touch a file that you then reference from your apps. Add something like config.vm.provision "shell", inline: "touch /etc/is_vagrant_vm" to the bottom of your Vagrantfile and base your conditionals around

问题 I a trying to setup this machine: https://github.com/ByteInternet/hypernode-vagrant When I do vagrant up i get following error: Timed out while waiting for the machine to boot. Full context of the error: $ vagrant up Bringing machine 'hypernode' up with 'virtualbox' provider... ==> hypernode: Will use PHP 7. If you want PHP 5.5 instead change the php version in local.yml. ==> hypernode: Checking if box 'hypernode_php7' is up to date... ==> hypernode: Clearing any previously set forwarded

问题 I have one site setup fine, but the second can't be accessed remotely: My YAML: --- ip: "192.168.10.10" memory: 2048 cpus: 1 provider: virtualbox authorize: ~/.ssh/id_rsa.pub keys: - ~/.ssh/id_rsa folders: - map: ~/Projects to: /home/vagrant/Projects sites: - map: app.app to: /home/vagrant/sites/app1/public - map: app2.app to: /home/vagrant/sites/app2/public port: 8100 ports: - host: 81 - guest: 8100 I can access the first site using my IP easily - http://192.168.0.5/ but the second one

问题 I think I messed up something simple, normally you should be able to instantly connect to your Vagrant VM using vagrant ssh . However, it's currently different for me. C:\Users\Sem\Documents\timeline>vagrant ssh Enter passphrase for key 'C:/Users/Sem/Documents/timeline/.vagrant/machines/default/virtualbox/private_key': vagrant@127.0.0.1's password: vagrant@127.0.0.1's password: vagrant@127.0.0.1's password: Permission denied (publickey,password). I found one other person having the same issue

问题 I'm using PuPHET tool to setup Vagrant so that a combo vagrant+puppet should just easily boot a VM with vagrant up. Im using a Centos64 setup - php 5.4, and some minor standard debug mode. Im running this on a Mac OSX Maverick. Here is the configuration: vagrantfile-local: vm: box: centos64-x64-vbox43-1383512148 box_url: 'http://box.puphpet.com/centos64-x64-vbox43.box' hostname: null network: private_network: 192.168.56.101 forwarded_port: OhyIDGb9LuDg: host: '7943' guest: '22' provider:

问题 I ran my virtual machine by the command "vagrant up" and it's ok. "vagrant ssh" work good and the output of ifconfig is: vagrant@precise32:~$ ifconfig eth0 Link encap:Ethernet HWaddr 08:00:27:12:96:98 inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0 inet6 addr: fe80::a00:27ff:fe12:9698/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:583 errors:0 dropped:0 overruns:0 frame:0 TX packets:420 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX

问题 system: Ruby: ruby 2.6.5p114 (2019-10-01 revision 67812) [x86_64-linux] Rails: Rails 6.0.2 OS: Windows to a VM (vagrant ssh -> to ubuntu machine : Linux vagrant-ubuntu-trusty-64 3.13.0-170-generic #220-Ubuntu SMP x86_64 GNU/Linux when I run rails server -b 0.0.0.0 I can access localhost:3000 and see the Yay! You’re on Rails! but when I attempt to navigate to localhost:3000/say/hello the below error comes up in browser Browser error: Showing /files_on_your_computer/rails6tut/demo/app/views

问题 I have an meanjs application running on a vagrant box. My vagrantfile is as follows config.vm.network "forwarded_port", guest: 27017, host: 27016 #mongodb config.vm.network "forwarded_port", guest: 1337, host: 1338 #node inspector config.vm.network "private_network", ip: "192.168.33.10" node inspector configuration is as follows 'node-inspector': { custom: { options: { 'web-port': 1337, 'web-host': 'localhost', 'debug-port': 5858, 'save-live-edit': true, 'no-preload': true, 'stack-trace-limit

问题 I have an meanjs application running on a vagrant box. My vagrantfile is as follows config.vm.network "forwarded_port", guest: 27017, host: 27016 #mongodb config.vm.network "forwarded_port", guest: 1337, host: 1338 #node inspector config.vm.network "private_network", ip: "192.168.33.10" node inspector configuration is as follows 'node-inspector': { custom: { options: { 'web-port': 1337, 'web-host': 'localhost', 'debug-port': 5858, 'save-live-edit': true, 'no-preload': true, 'stack-trace-limit