Your message dated Sun, 27 Aug 2023 23:00:59 +0000
with message-id <[email protected]>
and subject line Re: lxc: Please update lxc-debian.in in stable to allow native 
LXC creation on arm64
has caused the Debian Bug report #895432,
regarding lxc: Please update lxc-debian.in in stable to allow native LXC 
creation on arm64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
895432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895432
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lxc
Version: 1:2.0.7-2+deb9u2
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Setup an arm64 machine to run within a distributed system of multiple devices
which all need to use LXC.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Expected to be able to setup a native LXC on arm64 Stretch without extra 
options.
lxc-create -t debian -n server-unittests -- --release stretch --mirror 
http://ftp.uk.debian.org/debian/

   * What was the outcome of this action?

lxc-create: lxccontainer.c: create_run_template: 1297 container creation 
template for server-unittests failed

   * What outcome did you expect instead?

https://sources.debian.org/src/lxc/1:2.0.7-2+deb9u2/templates/lxc-debian.in/#L542
 lacks a mapping from
aarch64 to arm64 which is present in 
https://sources.debian.org/src/lxc/1:2.0.9-6/templates/lxc-debian.in/#L538

As this is a bug in LXC, please can an upload be arranged to update this 
template in Stretch?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 4.14.0-260-arm64 (SMP w/24 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lxc depends on:
ii  init-system-helpers  1.48
ii  libapparmor1         2.11.0-3+deb9u2
ii  libc6                2.24-11+deb9u3
ii  libcap2              1:2.25-1
ii  libgnutls30          3.5.8-5+deb9u3
ii  liblxc1              1:2.0.7-2+deb9u2
ii  libseccomp2          2.3.1-2.1
ii  libselinux1          2.6-3+b3
ii  lsb-base             9.20161125
ii  python3              3.5.3-1
ii  python3-lxc          1:2.0.7-2+deb9u2

Versions of packages lxc recommends:
ii  bridge-utils  1.5-13+deb9u1
ii  debootstrap   1.0.92~bpo9+1
ii  dirmngr       2.1.18-8~deb9u1
ii  dnsmasq-base  2.76-5+deb9u1
ii  gnupg         2.1.18-8~deb9u1
ii  iptables      1.6.1-2~bpo9+1
ii  libpam-cgfs   2.0.7-1
ii  lxcfs         2.0.7-1
ii  openssl       1.1.0f-3+deb9u2
ii  rsync         3.1.2-1+deb9u1
ii  uidmap        1:4.4-4.1

Versions of packages lxc suggests:
ii  apparmor     2.11.0-3+deb9u2
ii  btrfs-tools  4.13.3-1~bpo9+1
ii  lvm2         2.02.168-2

-- Configuration Files:
/etc/lxc/default.conf changed:
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up


-- no debconf information


-- 


Neil Williams
=============
http://www.linux.codehelp.co.uk/

Attachment: pgp2EDD2UvaNX.pgp
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Version: 1:3.1.0+really3.0.3-8

  It appears that a fix was never backported to stretch while it was
the stable release, but this issue would have been fixed with the
buster release. As there doesn't seem to be anything useful to do with
this bug now, I'm going to close it. If this is still an issue, please
re-open the bug (and assign to lxc-templates) with any relevant
information.

Mathias

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to