Baserock/ guides/ Baserock Tools: Common Errors

Using Baserock

Community

Background

Baserock Tools: Common Errors

  1. ERROR: no identities found
  2. Repeated prompts for root's password
  3. VirtualBox reports 'Nonexistent host networking interface'
  4. VirtualBox reports 'physical network interfaces were not found'
  5. VirtualBox reports 'Failed to attach the network LUN'

This page describes errors that may occur when setting up and using Baserock tools.

See The separate 'Build Issues' guide for errors when running morph build

morph Common Errors

ERROR: no identities found

If you see the error ERROR: no identities found when running ssh-add on the guest VM when following the steps in the Login to the development VM' section on the 'Quick Start' page or the 'Minimum Instructions' page. Check the following:

  • you have generated ssh keys on your host: these will be in files called id-rsa and id-rsa.pub in ~/.ssh/. If these files are not present, then run ssh-keygen - and accept the defaults;

  • when you ssh into you your guest, make sure you use the -A option. allowing your guest to use the keys from your host: e.g.

      ssh -A root@vm.ip.address

Repeated prompts for root's password

When running morph deploy or the cycle.sh script, you are repeatedly prompted for root's password on the guest system:

This happens when the ssh keys for communication between your host and guest machines are not properly configured.

Check that you have followed the steps in the Login to the development VM' section on the 'Quick Start' page.

VirtualBox reports 'Nonexistent host networking interface'

When starting a Baserock VM with VirtualBox, if you see the error

VBoxManage: error: Nonexistent host networking interface, name '' (VERR_INTERNAL_ERROR)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Console, interface IConsole

it is likely that the hostonly interface you added refers to a network adapter (wired or wireless) on your host that does not exist or is not configured correctly. For more information see

VirtualBox reports 'physical network interfaces were not found'

When starting a Baserock VM with VirtualBox the following error may appear;

Could not start the machine Baserock because the following physical network interfaces were not found:
en0 (adapter 1)
You can either change the machine's network settings or stop the machine.

This is because the bridged network interface must be an active network interface. You can see which interfaces are active by running ifconfig on your VM host.

VirtualBox reports 'Failed to attach the network LUN'

Similar to the above error, when starting a Baserock VM with VirtualBox the following error may appear;

VBoxManage: error: Failed to attach the network LUN (VERR_INVALID_PARAMETER)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Console, interface IConsole

This means that the BridgedInterface name is not being populated by VBoxManage. To resolve this, open the virtual machine's associated *.vbox file in a text editor, find the following line

<BridgedInterface name=""/>

and change it to

<BridgedInterface name="eth0"/>

Save and close the file, and the virtual machine should now boot as normal.