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.

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

BoxStarter not installed. The package was not found with the source(s) listed. #41

Closed
axcheron opened this Issue Nov 10, 2016 · 8 comments

Comments

Projects
None yet
4 participants
@axcheron

axcheron commented Nov 10, 2016

Hi,

I get an error when the provisioning process starts...

==> default: C:\Windows\system32>choco install BoxStarter
==> default: Chocolatey v0.10.3
==> default: Installing the following packages:
==> default:
==> default: BoxStarter
==> default: By installing you accept licenses for the packages.
==> default: BoxStarter not installed. The package was not found with the source(s) listed.
==> default:
==> default: If you specified a particular version and are receiving this message, it is possible that the package name exists but the version does not.
==> default: Version: ""
==> default: Source(s): "https://chocolatey.org/api/v2/"
==> default:
==> default: Chocolatey installed 0/1 packages. 1 packages failed.
==> default: See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
==> default:
==> default: Failures
==> default: - BoxStarter - BoxStarter not installed. The package was not found with the source(s) listed.
==> default: If you specified a particular version and are receiving this message, it is possible that the package name exists but the version does not.

I checked the connectivity on the VM, but everything is fine. Any ideas ?

System: OS X 10.11.6
VBox 5.1.8
Vagrant 1.8.6

Update 1

According to this issue: chocolatey/choco#1029, NAT seems to be the problem. I managed to manually install BoxStarter by changing my network adapter from NAT to Bridged, but of course it breaks Vagrant's port forward.

@jbarnett-r7

This comment has been minimized.

Show comment
Hide comment
@jbarnett-r7

jbarnett-r7 Nov 10, 2016

Contributor

Thank you for reporting this bug. We were actually seeing the same issue internally but hadn't been able to track down a root cause yet. I checked the issue thread you suggested and they suggested it might be a VirtualBox problem.

Sure enough I found this bug ticket on VirtualBox describing a similar issue. The thread there suggests trying a test build of VirtualBox, 5.1.9 r111846. I installed that one and the issue is no longer present.

Contributor

jbarnett-r7 commented Nov 10, 2016

Thank you for reporting this bug. We were actually seeing the same issue internally but hadn't been able to track down a root cause yet. I checked the issue thread you suggested and they suggested it might be a VirtualBox problem.

Sure enough I found this bug ticket on VirtualBox describing a similar issue. The thread there suggests trying a test build of VirtualBox, 5.1.9 r111846. I installed that one and the issue is no longer present.

jbarnett-r7 added a commit that referenced this issue Nov 10, 2016

@axcheron

This comment has been minimized.

Show comment
Hide comment
@axcheron

axcheron Nov 10, 2016

Thanks for your feedback. I downgraded VirtualBox from 5.1.8 to 5.1.6 and it works fine now.

axcheron commented Nov 10, 2016

Thanks for your feedback. I downgraded VirtualBox from 5.1.8 to 5.1.6 and it works fine now.

@jbarnett-r7

This comment has been minimized.

Show comment
Hide comment
@jbarnett-r7

jbarnett-r7 Nov 11, 2016

Contributor

Glad to hear it. I updated the docs to reflect the new requirements. I'll keep this issue open as a reminder to remove those requirements once the new version of VirtualBox is released

Contributor

jbarnett-r7 commented Nov 11, 2016

Glad to hear it. I updated the docs to reflect the new requirements. I'll keep this issue open as a reminder to remove those requirements once the new version of VirtualBox is released

@jbarnett-r7 jbarnett-r7 added bug and removed bug labels Nov 11, 2016

@Chiggins

This comment has been minimized.

Show comment
Hide comment
@Chiggins

Chiggins Nov 16, 2016

Maybe just because I'm running Arch Linux and it's pretty cutting edge, but I was able to get Metasploitable built and running. VBoxManage -v says 5.1.8r111374

Chiggins commented Nov 16, 2016

Maybe just because I'm running Arch Linux and it's pretty cutting edge, but I was able to get Metasploitable built and running. VBoxManage -v says 5.1.8r111374

@jbarnett-r7 jbarnett-r7 added the delayed label Nov 16, 2016

@semml0r

This comment has been minimized.

Show comment
Hide comment
@semml0r

semml0r Nov 17, 2016

Current build.sh script states the following:
sh build_win2008.sh A compatible version of VirtualBox was not found. Currently only 5.1.9 is supported. Please download and install it from https://www.virtualbox.org/wiki/Download_Old_Builds_5_1.
So this might be updated too, as 5.1.9 is not released as a public download. According to @axcheron it should point to version 5.1.6.

semml0r commented Nov 17, 2016

Current build.sh script states the following:
sh build_win2008.sh A compatible version of VirtualBox was not found. Currently only 5.1.9 is supported. Please download and install it from https://www.virtualbox.org/wiki/Download_Old_Builds_5_1.
So this might be updated too, as 5.1.9 is not released as a public download. According to @axcheron it should point to version 5.1.6.

@jbarnett-r7

This comment has been minimized.

Show comment
Hide comment
@jbarnett-r7

jbarnett-r7 Nov 17, 2016

Contributor

@semml0r That was my bad. I have that build installed locally so I was using that version when testing the script and forgot to fix it before committing. I just changed it back to 5.1.6.

Contributor

jbarnett-r7 commented Nov 17, 2016

@semml0r That was my bad. I have that build installed locally so I was using that version when testing the script and forgot to fix it before committing. I just changed it back to 5.1.6.

@jbarnett-r7

This comment has been minimized.

Show comment
Hide comment
@jbarnett-r7

jbarnett-r7 Jan 5, 2017

Contributor

The latest version of VirtualBox does not have this issue.

Contributor

jbarnett-r7 commented Jan 5, 2017

The latest version of VirtualBox does not have this issue.

@jbarnett-r7 jbarnett-r7 closed this Jan 5, 2017

@axcheron

This comment has been minimized.

Show comment
Hide comment
@axcheron

axcheron Jan 6, 2017

I also checked, VirtualBox 5.1.12 (r112440) works fine.

axcheron commented Jan 6, 2017

I also checked, VirtualBox 5.1.12 (r112440) works fine.

devec0 pushed a commit to devec0/metasploitable3 that referenced this issue Jun 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment