Subiquity - APT repo configuration issue

fcopetti

2/23/24, 8:59 AM

I'm trying to customize my ubuntu server installation by adding a custom apt repository. I added the following lines to the subiquity user-data yaml:

  apt:
    sources:
      my_repo:
        source: "deb https://...path.../1.0.0/x86_64/ stable main"
        key: |
          -----BEGIN PGP PUBLIC KEY BLOCK-----

          -----END PGP PUBLIC KEY BLOCK-----

the installation starts as expected but after a while it fails. After dropping to shell I looked at journalctl output and I see that the key is imported successfully, but when the apt update command runs the InRelease file is not validated:

The following signatures could not be verified because the public key is not available: NO_PUBKEY

I tried to chroot to the temporary installation dir and I see the key listed by the "apt-key list" command. I checked the fingerprint and is correct. if I run apt-key list on the installer rootfs I don't see the key listed.

On another pre-installed system the repository works like a charm.

Could it be that the repo files are validated against the keys of the installer rootfs and not to the ones of the installed system?

Thanks in advance.

0 + 0

package-management

apt

repository

subiquity

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Subiquity - APT repo configuration issue

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.