I had to use “sudo” on apt-update when I popped open a terminal in the appvm to see what the output would be. Of course I was the user in that instance. I mentioned it because the error message I got when I forgot to do so wasn’t obviously saying anything like “use sudo to do this.” The update checking itself apparently either runs as root, or does sudo or something; it doesn’t really matter.
I think I misinterpreted the point of making sure cacher doesn’t use itself. I thought you were indicating the update check wouldn’t work if cacher had the HTTPS stuff in it. That turns out not to be true; the update check works regardless of what the cacher wants to use for its proxy.
In the past I’ve never had any problems with the cacher’s template updating itself via the cacher…so long as the cacher exists when it does so!
Nope. You were right and clear @SteveC . I got turned around here. I was erroneously thinking that the changes to the repo files determined where the updates actually came from.
As a point of (possible) interest, I have it working quite well now.
I created appvms (limited memory, no network comm) for seven “key” templates, i.e. ones that I clone a lot to make other templates; and call them “Update Canaries” since their sole purpose is to warn me I need to update their templates. I can simply run them and wait a few minutes to see what needs updating, especially after a qube I am using flags an update. I run them to see how many templates need an update.
(Why bother? If I have some qube with a ton of apps installed on it and it needs an update, is it one of the apps, or the kernel? If the former, just that template, but if the latter, I have to update every template, and starting my “Update-Canary-00” will tell me that when its template (the clone granddaddy of all my VMs) shows up as needing an update. Otherwise, I’ll simply be playing update whack-a-mole when every qube I start up flags as needing an update.)
Today I had to update everything…then, apparently Firefox dropped an update and I had to update several templates again.
Before I got appvms working for detecting updates, I had to clone those TEMPLATES to update canaries (because I don’t want to run the original templates just to see if I need updates), and I had to update both them AND the template they were cloned from!