Hi Mark,

> Thanks for this. However Devuan doesn't fork any of the lxc pacakges and uses
> Debian's pacakges directly without recompilation. This is probably best included
> by submitting upstream, either to Debian or perhaps better
> https://linuxcontainers.org/.

I tend to disagree. Because

* linuxcontainers.org dropped support of templates other then "download".
They actively maintain only the "download" template.
* Now each distro. seems having responsibility to maintain its own version of
template, if that distro. is not satisfied with "download" template.
* Debian package maintainers maintains the Debian template, see
https://metadata.ftp-master.debian.org/changelogs//main/l/lxc-templates/lxc-templates_3.0.4-5_changelog
* "download" template only provides the limited choices of Devuan as
# lxc-create -n test -t download -- -d devuan
Setting up the GPG keyring
Downloading the image index

---
DIST    RELEASE    ARCH    VARIANT    BUILD
---
devuan    ascii    amd64    default    20210530_11:50
devuan    ascii    arm64    default    20210530_12:22
devuan    ascii    armel    default    20210530_12:07
devuan    ascii    armhf    default    20210530_12:22
devuan    ascii    i386    default    20210530_11:50
devuan    ascii    ppc64el    default    20210530_11:50
devuan    beowulf    amd64    default    20210530_11:50
devuan    beowulf    arm64    default    20210530_12:07
devuan    beowulf    armel    default    20210530_12:22
devuan    beowulf    armhf    default    20210530_11:50
devuan    beowulf    i386    default    20210530_11:50
devuan    beowulf    ppc64el    default    20210530_11:50
---

By the above observation, in my view,

(1) Attaching "upstream" to this issue is inappropriate. This is not an upstream issue.
(2) The question is whether or not Devuan is satisfied with "download"
template as above. If yes, attaching "wontfix" tag or closure of this issue is
appropriate.

Best regards, Ryutaroh