Sometimes users need to install software on TemplateVMs that is not available on the software respository for that templateVM’s distribution. But first please try the recommended (simpler and safer) method and to see if it’s available. In this post, I try to break down some of the alternatives.
Required reading: from the official docs on Trusting your TemplateVMs
There are at least 3 methods:
- Temporarily allowing networking for software installation
- Updates proxy
- Copy from another VM
Some examples of similar questions
I’m trying to build BitcoinArmory from source into a template VM but get the following error:
$ git clone git://github.com/etotheipi/BitcoinArmory.git
Cloning into ‘BitcoinArmory’…
fatal: unable to access ‘https://github.com/etotheipi/BitcoinArmory.git/’: Could not resolve host: github.com
– Zhang9000 at google groups
(method 1) Temporarily allowing networking for software installation
This is by far the easiest (GUI only), but you’re giving unchecked network access to the VM, but at least you don’t forget to turn it off (as would happen if you say connect it to sys-firewall).
Before proceeding, read this explanation from the docs about this process.
open the TemplateVM’s qube settings
on the “Basic” tab change networking to
sys-netsince sys-firewall enforces network isolation between qubes)
Important: go to the “Firewall rules” tab and select “Limit outgoing internet connections to…” and then on the bottom click the checkbox saying
Allow full network access for 5 min.
You then have 5 min to do the network required part for installing the program on the template.
Go back to the Qube settings “Basic” tab and set the
(solution based on this post)
(method 2) Updates proxy
The updates proxy is how templateVMs are able to update software, even though they’re not connected to the internet.
So if you want to
pip install or
git clone for example you can proxy those applications to the updates proxy (running on
Se bellow an example of this in practice
(method 3) Copy from another VM
You can also download the required files on another VM (or even a DisposableVM) and copy those files to the TemplateVM.