Subiquity crashes when using local apt mirror created with aptly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Instead of simply mirroring an apt repository (such as what apt-mirror does), aptly will download the debs, create its own structure and then generate new Release/InRelease files and sign them with its own locally generated gpg-key
If you use subiquity to install a server and points it to a local mirror created with aptly, there's no way for you to provide the gpg key and pass apt.conf.d arguments to let it install.
As a consequence, subiquity crashes when attempting to run "apt-get update" in-target:
2022-10-05 13:50:18,233 ERROR root:39 finish: subiquity/
More details:
https:/
Crash report:
https:/
Attempt to manually run the command (trying to mimic what subiquity does):
https:/
Using the following information in a user-data through an automated install will work:
apt:
primary:
- arches: [amd64, i386, default]
uri: http://
security:
- arches: [amd64, i386, default]
uri: http://
geoip: false
disable_suites: [backports, proposed]
disable_
conf: | # APT config
Acquire:
Acquire:
Acquire:
Acquire:
sources:
additional-
source: "deb http://
localrepokey:
key: | # full key as block
I think the answer here has to be some kind of modified ISO. It's not like we're going to get the user to type the public key in by hand, or even a fingerprint to be fetched from the keyserver (I guess we _could_ display the fingerprint of the key that signed the repo and ask the user if they trust it but .... hmm).