Page not found 404
But for me, creating and cloning template via salt doesn’t work
I’m sorry, only re-reading your post did I realize what it is you are asking for.
qvm-run --pass-io -u root
That’s just what you need to run a command inside a qube and passing the console output to your dom0 terminal. The
-u root makes sure the command runs as
root, so no
DEBIAN_FRONTEND='noninteractive' apt-get -o Dpkg::Options::='--force-confdef' -o Dpkg::Options::='--force-confold'
When you install the
apt-cacher-ng package manually, you will be presented with a screen asking you to choose some options. The above series of parameters makes it so there is no interactive dialog (noninteractive) and the package gets installed with the default options (confdef) and already existing configurations are not overwritten (force-confold).
Just the essentials, not extra packages please.
qubes-core-agent-networking qubes-core-agent-dom0-updates apt-cacher-ng -y"
… the packages and say ‘yes’ to any prompts.
If you are uncomfortable with the above, simply do this:
qvm-run my_template xterm… replace
my_templatewith the name of your template. This will give you a terminal window of your template.
Inside the template terminal window
sudo apt install --no-install-recommends qubes-core-agent-networking qubes-core-agent-dom0-updates apt-cacher-ngand then answer the prompts.
In any case, before someone else points it out again: if the above is gibberish to you and you feel the need to ask for clarification / unable to clarify the meaning yourself using a search engine of your choice … minimal templates and/or apt-cacher-ng maybe outside your current skill level and might lead to some frustration. Then again, that’s how you grow your skill level… so, you’ve been warned!
No, your previous reply matched my question
In your actual reply you mixed up the text format.
Unfortunately, I am busy with other tasks but setup Qubes based on minimal templates is the next chapter in my Qubes learning journey.
I will share my success, questions, summary next week.
Fixed it. It was a single missing character that did all that.
Just recently found out about this thread and I think it may just be the right place for a question I posted separately:
Long story short: I customized a debian-11-minimal AppVM which works fairly well with all usb block devices, except with Yubikeys. I’m convinced it must be a missing package because the classic debian-11 template handles it with no issues at all, but I can’t figure out which since I’ve already tried with
(Mind that all other necessary packages to normally handle a Yubikey have been installed)
I do have a separate
sys-usb but I excluded that’s the issue for the reason mentioned above.
I hope this doesn’t constitute thread hijacking!
Thank you all
Well, it is thread hijacking. Please answer this request in it’s dedicated thread and not here. Thank you!
My apologies, I thought it could’ve been a good idea given it’s related to a minimal template.
Added your RSS, I am looking forward to your minimizing Qubes, maximizing security guide.
I think there is 4. option here availble:
- Put “User” to “plugdev” group.
then you wont need passwordless sudo package and can still mount external devices.
2 posts were split to a new topic: Debian-minimal template for sys-audio
Hi @Sven could you please share your status on this?
Looking forward to your how-to
@whoami … by Sunday evening / Monday morning CST. You successfully shamed me into action.
I very interested in the salt part…
As soon as I find some free time I will follow your instructions on a fresh installation.
But do not stress, no urgency.
Yeah, it’s only gonna be a guide about the bash script stuff. Kind of an updated more detailed version of the above post.
Not sure if and when I’ll get into salt.
OK, let’s get this started: Automate debian-minimal based template creation
How does this respond to
- sys-usb can see the files anyway
- I don’t view or edit any files inside sys-usb (which I believe to be the concern with accessing files in sys-usb)
- my sys-usb doesn’t have any programs installed (minimal template)
- I no longer mount encrypted volumes in sys-usb (that’s where the FAQ applies)
It is obviously a bad idea to mount an encrypted partition inside an untrusted qube. It’s bad practice and bad advice.
I will edit both in the forum and on my website to correct this mistake in the next days.
At the time, your post stuck in my mind, and I posted it yesterday because I read the docs again (and constantly over and over again) and stumbled upon this, and I had no doubt how you’d react, but I needed it to create that way for users hopefully an example of a good practice of a constant re-reading, re-thinking and revising, eventually to realizing what many of us already did: that Qubes is life-changer, milestone.