An official architecture is not always available in testing. New
architectures get added to unstable first, and only some time after that
they *may* get added to testing as well. This is just now happening with
riscv64, and checking whether it's available in testing will *not* give
the correct answer for the question "is this an official Debian
architecture?".
Also, since debian-ports only contain unstable, just refuse to use
debian-ports if not creating an unstable/sid container.
Signed-off-by: Antonio Terceiro <terceiro@debian.org>
--force-yes is deprecated, and is a shortcut for
--allow-unauthenticated, --allow-downgrades, --allow-remove-essential,
--allow-change-held-packages. --allow-unauthenticated is the only
likely to be needed here, so instead of allowing unauthenticated
packages, copy any custom keyring used inside the rootfs so any packages
we need to install are properly authenticated. The common case is
debian-ports-archive-keyring.
Signed-off-by: Antonio Terceiro <terceiro@debian.org>
This allows them to be executed directly, and symlinked from
/usr/share/lxc/templates/ to the build directory for easier testing with
a system-installed lxc.
Signed-off-by: Antonio Terceiro <terceiro@debian.org>
When trying to create containers for unnoficial Debian architectures,
use different defaults for mirror and keyring, install
debian-ports-archive-keyring, and default release to unstable. This way
one can create containers for unnoficial architectures without having to
pass several extra parameters.
Signed-off-by: Antonio Terceiro <terceiro@debian.org>
This makes it possible to create containers for unofficial
architectures such as the ones on ports.debian.org, by specifying a
custom mirror and its associated keyring.
Signed-off-by: Antonio Terceiro <terceiro@debian.org>
Antonio Terceiro