evernym
VirtualBox: Setting Up a Test Sovrin Network in VMs
I'm following the steps here (https://github.com/evernym/sovrin-environments/blob/master/vagrant/training/vb-multi-vm/TestSovrinClusterSetup.md) to setup test sovrin network (MacOS, VirtualBox, vagrant). I'm able to successfully ssh to an agent but then it's not able to understand 'sovrin' command.
$ vagrant ssh agent04 vagrant@agent04:~$ sovrin sovrin: command not found
Rupert: first, double-check to see if sovrin's client package is installed (dpkg -l | grep sovrin). (When using vagrant, I've seen a few cases where timing in the vagrant startup has been unusual, and a command hasn't run as expected.) If the package is not installed, try doing so: apt install sovrin-client. If the package is installed, test which user you are and whether sovrin is in your path. You might try uninstalling (apt remove sovrin-client) and then re-installing (apt install sovrin-client).
The document does not mention installation of sovrin-client. I was expecting already built in the VMs. What you are suggesting makes complete sense.
However, 'apt install sovrin-client' fails... vagrant@agent04:~$ sudo apt-get install sovrin-client Reading package lists... Done Building dependency tree... Done E: Unable to locate package sovrin-client
Can't find the package on Ubuntu portal either
If you can't install sovrin-client with apt, then it means you don't have /etc/apt/sources.lst configured correctly inside the VM. You will need to add a public key for signed .deb files, and then add https://repo.evernym.com and https://repo.sovrin.org. These steps are performed by the vagrant scripts, which is why I am so puzzled. @mgbailey or @trevharmon, do you have any suggestions?
BTW, the instructions for adding a public signing key and modifying /etc/apt/sources.lst are mentioned here: https://docs.google.com/document/d/1Da6adGCoRhCntQwPQPzz1H1dJRHAmgyyDi0k01ncvuw/edit
Please open the vagrant script in your VM, and copy each line of it and execute it from the command line. If there is a breakdown somewhere, that should isolate it.
Mike
On Mon, Jun 19, 2017 at 4:07 PM, Daniel Hardman [email protected] wrote:
BTW, the instructions for adding a public signing key and modifying /etc/apt/sources.lst are mentioned here: https://docs.google.com/ document/d/1Da6adGCoRhCntQwPQPzz1H1dJRHAmgyyDi0k01ncvuw/edit
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/evernym/sovrin-environments/issues/10#issuecomment-309587384, or mute the thread https://github.com/notifications/unsubscribe-auth/AFXuAJNE5OjJlewJqPEkaJ4kTzm3RYoCks5sFvESgaJpZM4N8j3j .
@mgbailey What is the path to the vagrant script inside the VM? And should this script's commands be run as root?
These Vagrant files mount /vagrant as part of startup. The startup scripts are found in a sub-directory there. Because of how Vagrant works, the initialization scripts are always run as root, so at times one needs to drop privileges in order to get things to work.
