Closed Vasu77df closed 2 months ago
@Vasu77df We need the keyring on the host to build the tools tree image. Isn't that the issue here?
@Vasu77df Ping?
@DaanDeMeyer , sorry about the delayed response, and thank you for taking a look at this. Now thinking about it, it makes sense, yes, to build the tools tree we do need to the host's keyring. On this matter we can close this issue.
I have a question, on whether mkosi will support any other Mirror=
or ToolsTreeMirror=
keyring other than the ubuntu-archive-keyring.gpg
for ubuntu and the equivalent for debian? Are there any plans to support a user defined key for the main Mirror?
Understanding from this line it's hardcoded to a specific key.
@Vasu77df We generally assume the mirrors are signed with the same key. If you want to use a different one, you can override it by putting your own key in the same location using PackageManagerTrees=
.
For any other questions, please use the discussions tab in github or join the matrix channel
mkosi commit the issue has been seen with
23.1
Used host distribution
Debian bookworm
Used target distribution
Ubuntu noble
Linux kernel version used
6.8.11-200.fc39.x86_64
CPU architectures issue was seen on
x86_64
Unexpected behaviour you saw
From my understanding of ToolsTreeCertificates option from this line in the mkosi docs:
When ToolsTree is enabled and ToolsTreeCertificates is enabled,
mkosi
, will look for gpg keys in the tools image and not the host, but that does not seem to be the case forubuntu
,debian
, or rather theapt.py
installer.I suspect the explicit path in signedby lines here is the issue:
Used mkosi config
mkosi output