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.

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

no longer working (?) #5

Open
asloan7 opened this issue Jun 16, 2015 · 3 comments
Open

no longer working (?) #5

asloan7 opened this issue Jun 16, 2015 · 3 comments

Comments

@asloan7
Copy link

asloan7 commented Jun 16, 2015

Hi, tried running this from your blog post http://blog.howareyou.com/post/62157486858/continuous-delivery-with-docker-and-jenkins-part

Used current pieces VirtualBox-4.3.28-100309-Win.exe, Oracle_VM_VirtualBox_Extension_Pack-4.3.28-100309.vbox-extpack, vagrant_1.7.2.msi, Git-1.9.5-preview20150319.exe

This is what happened:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'ubuntu' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Adding box 'ubuntu' (v0) for provider: virtualbox
default: Downloading: http://files.vagrantup.com/precise64.box
default: Progress: 100% (Rate: 577k/s, Estimated time remaining: --:--:--)
==> default: Successfully added box 'ubuntu' (v0) for 'virtualbox'!
==> default: Importing base box 'ubuntu'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: hi_sinatra-docker_default_1434409184461_11936
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
default: Adapter 3: hostonly
default: Adapter 4: hostonly
default: Adapter 5: hostonly
default: Adapter 6: hostonly
default: Adapter 7: hostonly
default: Adapter 8: hostonly
default: Adapter 9: hostonly
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "928e9c53-0b37-4d63-9d33-33623337ea8f", "--nic1", "nat", "--nic2", "hostonly",
"--hostonlyadapter2", "VirtualBox Host-Only Ethernet Adapter #2", "--cableconnected2", "on", "--nic
3", "hostonly", "--hostonlyadapter3", "VirtualBox Host-Only Ethernet Adapter #2", "--cableconnected3
", "on", "--nic4", "hostonly", "--hostonlyadapter4", "VirtualBox Host-Only Ethernet Adapter #2", "--
cableconnected4", "on", "--nic5", "hostonly", "--hostonlyadapter5", "VirtualBox Host-Only Ethernet A
dapter #2", "--cableconnected5", "on", "--nic6", "hostonly", "--hostonlyadapter6", "VirtualBox Host-
Only Ethernet Adapter #2", "--cableconnected6", "on", "--nic7", "hostonly", "--hostonlyadapter7", "V
irtualBox Host-Only Ethernet Adapter #2", "--cableconnected7", "on", "--nic8", "hostonly", "--hoston
lyadapter8", "VirtualBox Host-Only Ethernet Adapter #2", "--cableconnected8", "on", "--nic9", "hosto
nly", "--hostonlyadapter9", "VirtualBox Host-Only Ethernet Adapter #2", "--cableconnected9", "on"]

Stderr: VBoxManage.exe: error: Invalid NIC number 9
VBoxManage.exe: error: Invalid NIC number 9
VBoxManage.exe: error: Invalid NIC number 9

@bestie
Copy link

bestie commented Jun 17, 2015

I'm not sure anyone is supporting this project anymore, if you get in touch with @gerhard who wrote the original blog post he might be able to help.

@gerhard
Copy link
Contributor

gerhard commented Jun 18, 2015

@asloan7 this seems to be a Vagrant issue, specifically Vagrant on Windows. I'm not a Windows user, but I would start at the private network Vagrant config and find an alternative way to NFS dir sharing. You will also need to setup port forwarding for Jenkins as you won't have a private IP address.

@asloan7
Copy link
Author

asloan7 commented Jun 18, 2015

Tried a 2nd time, looks like it went further - but now have to find out why VirtualBox is digging up an older version of extensions

==> default: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version of
default: VirtualBox! In most cases this is fine, but in rare cases it can
default: prevent things such as shared folders from working properly. If you see
default: shared folder errors, please make sure the guest additions within the
default: virtual machine match the version of VirtualBox you have installed on
default: your host and reload your VM.
default:
default: Guest Additions Version: 4.2.0
default: VirtualBox Version: 4.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants