This page describes errors that may occur when setting up and using Baserock tools.
See The separate 'Build Issues' guide for errors when running
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
~/.ssh/. If these files are not present, then run
ssh-keygen- and accept the defaults;
sshinto you your guest, make sure you use the
-Aoption. allowing your guest to use the keys from your host: e.g.
ssh -A firstname.lastname@example.org
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.
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
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.
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
and change it to
Save and close the file, and the virtual machine should now boot as normal.