Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

error in instance.rb #29

Closed
elieyal opened this issue Nov 21, 2016 · 3 comments
Closed

error in instance.rb #29

elieyal opened this issue Nov 21, 2016 · 3 comments
Labels
bug

Comments

@elieyal
Copy link

elieyal commented Nov 21, 2016

Hi,
I am new to this and I'm trying to bring up the VM using Vagrant. I have downloaded the files into a new directory and ran "vagrant up" command but I get this error:
C:\vagrant>cd pentest-env-master

C:\vagrant\pentest-env-master>vagrant up
C:/vagrant/pentest-env-master/lib/pentestenv/instance.rb:18:in initialize': Spe cified instance kalinot found. (ArgumentError) from C:/vagrant/pentest-env-master/lib/pentestenv/customization.rb:18:innew'
from C:/vagrant/pentest-env-master/lib/pentestenv/customization.rb:18:in
block in register' from C:/vagrant/pentest-env-master/lib/pentestenv/customization.rb:17:in each'
from C:/vagrant/pentest-env-master/lib/pentestenv/customization.rb:17:in
register' from C:/vagrant/pentest-env-master/Vagrantfile:21:in block in <top (req
uired)>'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c
onfig/v2/loader.rb:37:in call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c onfig/v2/loader.rb:37:in load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c
onfig/loader.rb:113:in block (2 levels) in load' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c onfig/loader.rb:107:in each'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c
onfig/loader.rb:107:in block in load' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c onfig/loader.rb:104:in each'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c
onfig/loader.rb:104:in load' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/v agrantfile.rb:28:in initialize'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/e
nvironment.rb:746:in new' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/e nvironment.rb:746:in vagrantfile'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/e
nvironment.rb:492:in host' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/e nvironment.rb:214:in block in action_runner'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/a
ction/runner.rb:33:in call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/a ction/runner.rb:33:in run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/e
nvironment.rb:479:in hook' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/e nvironment.rb:728:in unload'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/bin/vagrant:1
92:in ensure in <main>' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/bin/vagrant:1 92:in

'

C:\vagrant\pentest-env-master>

I have not changed anything. is this how it is supposed to be? maybe I have made a wrong configuration somewhere?
@Sliim
Copy link
Owner

Sliim commented Nov 22, 2016

Hi!
Do you have a file called kali.rb in C:\vagrant\pentest-env-master\instances?

@Sliim Sliim mentioned this issue Nov 22, 2016
Closed
@R3zk0n
Copy link

R3zk0n commented Nov 25, 2016

Hi mate, having the same error as the person above, ive got kali.rb in the instances path. Sorry if its a just a small thing, not use to use vagrant.

Sliim added a commit that referenced this issue Dec 13, 2016
@Sliim
Improved Pentestenv::Instance.instance_path method
6bf892b 
Use File.expand_path to get instances/targets absolute path and
Dir.pwd instead of PWD envvar to get current working directory.
This should fix windows issues such as #29
@Sliim
Copy link
Owner

Sliim commented Dec 13, 2016

Hi,
Can you pull the master branch and retry? I think this is an issue with windows path..

@Sliim Sliim added the bug label Dec 13, 2016
@Sliim Sliim closed this as completed Jan 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Sliim @R3zk0n @elieyal