Thank you.
But why? LXC is enough and the problems depend on devuan startup problems (not solved)
and would not be different using incus. No containers (and additionally, no (k)vms) are coming
up at boot and the cgroups dont work in containers.
Although is see lcxfs running, the problem goes away, if I restart it (which, naturally, dont help
for the boottime).
Never have had such a problem the years before (using only debian).

Regards,
Manfred

But this does not help, because in a pure container, there is NO pgp.
I have had that problem earlier and it looks, the bug with lxc-templates has never been solved, a continuing PITA
(and there is really a lot more with this - but I dont try to mix everything).
There has been an older post of mine in galaxy:

https://dev1galaxy.org/viewtopic.php?id=6683

where 'fsmithre' posted this link to the key:

https://pkgmaster.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring_2023.05.28_all.deb

Now I used this on the lxc-host and downloaded it using curl and then moved it into the container,
where I installed it using:

dpkg -i /ops/install/local/misc/devuan-keyring_2023.05.28_all.deb

apt update

succeeds now.
The devuan pages about the keys ars a mysterious for me and are not of any help.
But thanks for yours

Regards,
Manfred

And this forum adds to the nightmare, you have to study about to post a link the right way!

The following errors need to be corrected before the message can be posted:

    [url] was opened within itself, this is not allowed

(I rewotre the url to use code instead ....
No wonder, Linux has sooo many users ....
After 40 years of IT, Linux became my biggest annoyance.

you could try this approach which has helped me install drivers for my graphic card;

i thinkg you can install it with another name if you so like (instead of "amdgpu")

there use to be tool "apt-key" or "add-apt-key" or similar, but that is no longer funciton.

this command found on github, it does function also for devuan.

just insert your key, and it could be ready to go, hopefully.

I installed a lxc-container, but I cannot install software in it.
I am doing it on a debian host (debian 11, kernel 6.1).
Because I need basic software (like nano), after setting up the container, I usually install same packages (like nano) using
chroot and start with apt update:

chroot /var/lib/lxc/devu5t2/rootfs apt update

But this failes with this message:

Get:1 http://deb.devuan.org/merged daedalus InRelease [43.0 kB]
Get:2 http://deb.devuan.org/merged daedalus-updates InRelease [32.7 kB]
Err:1 http://deb.devuan.org/merged daedalus InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB
Err:2 http://deb.devuan.org/merged daedalus-updates InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.devuan.org/merged daedalus InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB
W: GPG error: http://deb.devuan.org/merged daedalus-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 94532124541922FB
E: The repository 'http://deb.devuan.org/merged daedalus-updates InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

How can I proceed?
This is - sad to say - not really new to me and seems to show a peristent bug.
Edit:
The keyring is installed:

$ acp devuan-keyring
devuan-keyring:
  Installed: 2023.05.28
  Candidate: 2023.05.28

BTW, this shows (over and over again), that a secure OS requires direct internet access:
GPG has to proxy configuration, an "open pain".

Some help would be great!

Thanks,
Manfred