Do i need to wipe the private volume for the template vm if so how?
EDIT: I figured it out was because the template vm changes dont take effect until the template is shutdown. Took me way to long to figure that out.
You must log in or register to comment.
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 57 users / day
- 383 users / week
- 1.5K users / month
- 5.7K users / 6 months
- 1 subscriber
- 3K Posts
- 75.4K Comments
- Modlog
/etc/skel is highly distribution specific.
Are you sure your VM even pulls from it automatically versus needing some sort of manual action?
My template is debian based so /etc/skel should be fine. My understanding is that qubes makes a private volume that it mounts into /home and some other dirs but thats the only non volatile part. When u create a new app vm from the template vm the private volume of the template is thrown away and a new one created this should create a new user that should be templates from /etc/skel but thats not happening idk why
You’re looking for something hyper specific. I’d say check in the forums like the other comments said. Else actually debug and check that the file you mean to exist actually exists on VM boot. You have a chicken and egg scenario, and the first step is logs.
Alright just checked the files I want are in the app vms /etc/skel so idk