FHIR Chat · Vagrant Sandbox Install Errors · smart

Stream: smart

Topic: Vagrant Sandbox Install Errors


view this post on Zulip Patrick Werner (Dec 14 2016 at 13:18):

I tried to install the smart-on-fhir sandbox via Vagrant on a Ubuntu 16.04 machine and experienced the following issues:
- be sure to have VT-x enabled, without it the virtualbox won't boot.
- Vagrant 1.8.1 in Ubuntu 16.04 has a bug related to install vagrant plugins:
https://github.com/mitchellh/vagrant/issues/7073
Workaround: Install Vagrant 1.9.1 .deb from Vagrant Homepage via dpkg
- Network error, cable unplugged -> SSH timeout
another known Bug in VirtualBox(Ubuntu uses 5.0.24 - bug is fixed in 5.0.28)
https://github.com/chef/bento/issues/688
Workaround: Insert "vb.customize ["modifyvm", :id, "--cableconnected1", "on"]" in the VagrantFile

view this post on Zulip Patrick Werner (Mar 01 2017 at 11:58):

Hi, today i tried to install the smart vagrant sandbox with the new installer: https://github.com/smart-on-fhir/installer
It failed at:

TASK [apps-code : checkout cardiac risk app] ***********************************
fatal: [default]: FAILED! => {"changed": false, "cmd": "/usr/bin/git checkout --force v0.1.0", "failed": true, "msg": "Failed to checkout v0.1.0", "rc": 1, "stderr": "error: pathspec 'v0.1.0' did not match any file(s) known to git.\n", "stdout": "", "stdout_lines": []}

view this post on Zulip Dan Gottlieb (Mar 01 2017 at 13:44):

@Travis Cummings - any suggestions?

view this post on Zulip Patrick Werner (Mar 01 2017 at 15:42):

i'm currently debugging the error (unfortunatly i'm a Vagrant/ansible noob. It seems, that only the first invocation of the git task fails. If i run vagrant provision the former failing git task completes, and the next one fails. Then rerun ... next one fails

view this post on Zulip Pascal Pfiffner (Mar 01 2017 at 21:01):

The message you're getting means that it's trying to checkout the v0.1.0 tag, which it cannot find.

view this post on Zulip Patrick Werner (Mar 03 2017 at 12:58):

@Pascal Pfiffner i got that. But it is actually a bug in my ansible version: 2.2.1.0: https://github.com/ansible/ansible/pull/18730
If you don't want to downgrade your ansible installation just trigger vagrant provision several times (every git task needs two runs each to work)


Last updated: Apr 12 2022 at 19:14 UTC