search

apeunit / LaunchControlD

LaunchControl orchestration and deployment service
MIT License
1 stars 0 forks source link

Cannot use builtin driver virtualbox #4

Closed randomshinichi closed 4 years ago

randomshinichi commented 4 years ago 
evtvzd events new --token EVTX -m v1@email.com --stake 10000 --owner owner@email.com --provider virtualbox --debug

Using config file: /home/shinichi/source/work/evtvzd/config.yaml
Preparing the environment
Summary:
there are 1 validators
each with 10000 stake
and a total coinbase of 1000000000EVTX
that will be distributed over the 1 validators (~ 1000000000EVTX each).
Finally will be deploying 1 servers+nodes (1 for each validators) on virtualbox
Shall we proceed? [Y/n]:
Here we go!!
INFO[0001] Node ID for v1@email.com is evtx-d97517a3673688070aef-0 
DEBU[0001] DeployEvent cmd: /tmp/workspace/bin/docker-machinevirtualboxevtx-d97517a3673688070aef-0 
DEBU[0001] DeployEvent env vars set to [HOME=/tmp/workspace/evts/evtx-d97517a3673688070aef PATH=/tmp/workspace/bin] 
ERRO[0005] cmd.Run() failed with exit status 3, Running pre-create checks...
Error with pre-create check: "VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path"
The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.

There was an error, run the command with --debug for more info: exit status 3
Operation completed in 5.486543876s

It does not find my VBoxManage which is in /usr/bin. Please reconsider how the PATH is determined, it's probably under pkg/evtvzd/docker.go:DeployEvent()

noandrea commented 4 years ago

I wanted to restrict the PATH env var for security reasons, but I can see that there is a point for this particular use case