I appreciate all the responses. The AppVM approached turned out to be ideal anyway: what didn't get installed via pip to the templateVM got installed to a dedicated OSINT "template" AppVM. That way, like steve suggested, I can clone it at will so I can have a clean start point each time.
As an aside, I don't mind the learning curve honestly for this OS, I love it. I just had to learn to actually talk and ask for help when it comes to troubleshooting issues I come across. The OS itself is a little intimidating for a novice, but all it takes is some work. Appreciate this response steve, thank you it did help. On Sunday, June 6, 2021 at 2:54:18 PM UTC-4 [email protected] wrote: > On 6/6/21 2:12 PM, Chrome wrote: > > Hello there all, > > > > I am currently following the instructions to create an OSINT VM > > Michael Bazzell's "Open Source Intelligence Techniques 8th Edition." > Its a good book. I do wish he had a chapter for Qubes in it. I think the > only reason Michael doesn't push Qubes as a platform is that it has a > steep learning curve that not many are willing to take on. If you do > Qubes anyway and the learning curve is Ok, then you will find Qubes to > be a much more flexible platform in the long run. > > Naturally I'm trying to avoid installing a whole new OS (Ubuntu is > > recommended by the author) or to have a dedicated laptop for this. I > > figured it would be a fun experiment to see how far I could get with > > Qubes before I ran into problems. > > All the way I'm sure. > > > So far, issues are minor but when I hit a roadblock, like the below > > terminal text, I'm ill-prepared to troubleshoot it myself. Can someone > > help me understand what I'm looking at and how to fix it so I can > > install packages via pip onto my Fedora templateVM? Thank you > > First templates do not have network access by default so you may need a > proxy setup. > > > https://qubes-os.discourse.group/t/when-to-assign-templatevms-a-network-connection/4307/2 > > > By default pip needs/wants to install directly into the system space > (/usr/local/) which on a template is not shared with the AppVM. Because > this directory is not even presented to an AppVM file system it wont be > useable in the AppVM. It would need to be installed in the AppVM itself > if you want it installed in /usr/local. > > The problem is, security wise, its a bad idea to run foreign code (pip's > package installer scripts) as root in a template. You could easily > compromise every AppVM on the system by introducing malicious code. That > is way pip was warning about running as root. > > But if you use the "--user" flag as the error message says then pip can > install the packages an AppVM with everything installed into the user's > home directory. That way the user has control over the env and can > choose which environment they want to use. > > If you were wanting to have the ability to start from a pristine > starting point for each user session then you might want to either to > create a dvm or create a default AppVM which can be cloned as often as > you like. > > > Relevant Terminal text: > > [user@fedora-32 ~]$ sudo -H python3 -m pip install instalooter > > > https://stackoverflow.com/questions/42988977/what-is-the-purpose-of-pip-install-user > > > $ sudo -H python3 -m pip install --user instalooter > > The above will install in the users directory instead > > > WARNING: Running pip install with root privileges is generally not a > > good idea. Try `python3 -m pip install --user` instead. > > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f0eb7419-bc65-4362-ab34-c42a03c98990n%40googlegroups.com.
