Building Debian from Ubuntu fails on keyring check

[curranbrandt]

I am trying to build an Ubuntu 22 server image, from an interim Debian host. I am using the default ToolsTree, and my tree builds just fine. Then, when trying to build the Ubuntu image, it fails on an ubuntu-keyring check, as it the necessary Ubuntu keyring not in /usr/share/keyrings.

I have tried fixing this with two approaches:

1. Install keyring to build tree/Debian container via ToolsTreePackages=ubuntu-keyring
   This should ensure that even if keychecks occur, the tool tree has the proper keyring needed to verify Ubuntu sources and packages
2. Ignore keychecks entirely
   RepositoryKeychecks=false
   This should instruct the build environment to skip keychecks for packages when building the target image?

Sadly, neither of these seem to fix my issue. Mkosi summarize does not list any additional packages for my Debian Testing build tree/image.

I initially thought that my target Ubuntu fs would need the keyring, but it seems that it is the Debian tools tree that needs it in order to download and install Ubuntu packages into the target fs/image.

For now, I just grab the ubuntu keyring and stick it in mkosi.tools/usr/share/keyrings, along with all of the Debian ones. Ideally I would be able to account for this in my mkosi config... is there a better way? Goal is to use a Makefile with targets, so I want my mkosi build to work first go.

Thanks!

[MoltenArmor]

Can't reproduce this. Can you attach your mkosi.conf content and mkosi version?

[curran-brandt]

Yep! Here is my error:

% mkosi build
‣ Validating certificates and keys
‣ Keyring for repo http://archive.ubuntu.com/ubuntu not found at /usr/share/keyrings/ubuntu-archive-keyring.gpg
‣ (Make sure the right keyring package (e.g. debian-archive-keyring, kali-archive-keyring or ubuntu-keyring) is installed)
tput: unknown terminal "xterm-ghostty"
tput: unknown terminal "xterm-ghostty"
% ls -ld mkosi.tools
drwxr-xr-x - curran 31 Dec  1979 mkosi.tools

And here is my config:

% cat mkosi.conf
[Output]
Format=disk
Output=protectli_baseline.image
ImageId=Protectli
ImageVersion=0.0
#SecureBoot=on

[Distribution]
Distribution=ubuntu
Release=jammy
Architecture=x86-64
#Repositories=main,universe
#

[Build]
ToolsTree=default
ToolsTreePackages=ubuntu-keyring
ToolsTreeProfiles=runtime,misc
#ToolsTreePackages=git
ToolsTreeCertificates=false
History=yes
Incremental=yes
WithNetwork=true
CacheDirectory=./mkosi.cache

[Content]
Bootable=yes
# ftw
Bootloader=systemd-boot

Packages=linux-image-amd64
        apt
        base-files
        build-essential
        curl
        gpg
        iproute2
        iputils-ping
        isc-dhcp-client
        less
        linux-image-generic
        man
        nano
        openssh-server
        python3
        software-properties-common
        sudo
        systemd
    udev
        vim
#MakeInitrd=no

Autologin=true
Ssh=true
KernelCommandLine=rw
# KernelCommandLine=rw


# This has a bunch of the _sane_ base packages
[Include]
Include=mkosi-vm

[MoltenArmor]

I'm still unable to reproduce this with your mkosi.conf.

You can try the following steps, and check whether your issue is resolved:

1. Run mkosi clean -ff.
2. Upgrade mkosi to the latest version (from the main branch).
3. Try building again.

[curranbrandt]

Rgr, thanks. Got it resolved!