Your message dated Sun, 12 Nov 2023 17:47:26 +0000
with message-id <e1r2eyq-006rne...@fasolo.debian.org>
and subject line Bug#1053821: fixed in crun 0.17+dfsg-1+deb11u2
has caused the Debian Bug report #1053821,
regarding crun: kernel 6.1.0-13 (6.1.55) breaks compatibility with crun < 1.9.2
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 ow...@bugs.debian.org
immediately.)


-- 
1053821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: crun
Version: 1.8.1-1+b1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   The release of kernel 6.1.0-13 (6.1.55) included a change ('attr: block mode 
changes of symlinks') which
   breaks running containers that use systemd (like Debian itself) as
   the init system.

   This issue was recognized on the crun issue tracker:
   1. https://github.com/containers/crun/issues/1308
   2. https://github.com/containers/crun/pull/1309

   Reproduction instructions are here:
   1. https://github.com/containers/crun/issues/1308#issuecomment-1731077226

   The offending kernel commit is here:
   1. 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5d1f903f75a80daa4dfb3d84e114ec8ecbf29956

   Which shows up in this changelog:
   1. 
https://metadata.ftp-master.debian.org/changelogs//main/l/linux-signed-amd64/linux-signed-amd64_6.1.55+1_changelog

   The end result is that running the current version of crun with
   kernel 6.1.0-13 (6.1.55) means that containers using systemd as their
   init system will fail to run with an error like the following:

   'Error: OCI runtime error: crun: chmod `run/shm`: Operation not supported'

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     I ran a container that uses systemd as an init system, following
     the instructions listed here: 
     https://github.com/containers/crun/issues/1308#issuecomment-1731077226
   * What was the outcome of this action?
     An error message like the following:
     'Error: OCI runtime error: crun: chmod `run/shm`: Operation not supported'
   * What outcome did you expect instead?
     The container to run properly.

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


-- System Information:
Debian Release: 12.2
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages crun depends on:
ii  libc6        2.36-9+deb12u3
ii  libcap2      1:2.66-4
ii  libseccomp2  2.5.4-1+b3
ii  libsystemd0  252.17-1~deb12u1
ii  libyajl2     2.1.0-3+deb12u2

crun recommends no packages.

crun suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: crun
Source-Version: 0.17+dfsg-1+deb11u2
Done: Faidon Liambotis <parav...@debian.org>

We believe that the bug you reported is fixed in the latest version of
crun, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1053...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Faidon Liambotis <parav...@debian.org> (supplier of updated crun package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 02 Nov 2023 18:52:46 +0200
Source: crun
Architecture: source
Version: 0.17+dfsg-1+deb11u2
Distribution: bullseye
Urgency: medium
Maintainer: Dmitry Smirnov <only...@debian.org>
Changed-By: Faidon Liambotis <parav...@debian.org>
Closes: 1053821
Changes:
 crun (0.17+dfsg-1+deb11u2) bullseye; urgency=medium
 .
   * Backport two commits from upstream ("ignore ENOTSUP when chmod a
     symlink"), that restore containers with systemd as their init system, when
     running under Linux >= v6.6, >= v6.1.55 and >= 5.10.197, i.e. bullseye's
     and bookworm's current stable kernels. (Closes: #1053821)
Checksums-Sha1:
 270fb1f5d635c941211cffe2e6f70a149f481df7 2153 crun_0.17+dfsg-1+deb11u2.dsc
 f450017eaafc917d918feebba9e6fa5d5a75bb2f 16236 
crun_0.17+dfsg-1+deb11u2.debian.tar.xz
 a142bd9ad4935efd48f30d548cdb0815f10048bb 7391 
crun_0.17+dfsg-1+deb11u2_source.buildinfo
Checksums-Sha256:
 b6919513f8aa3ed373de3b69b3490bf8dc6bdc22ff2b06a8ed3ad483ef420a6a 2153 
crun_0.17+dfsg-1+deb11u2.dsc
 58b0ddcc5e6709915a9eed3f39890bd0f4db59a45510b4e0fea9d3eedc683082 16236 
crun_0.17+dfsg-1+deb11u2.debian.tar.xz
 b1dee38b7308a3268ead61c68f06aef56cf76041b16508081d54f6b70b90524a 7391 
crun_0.17+dfsg-1+deb11u2_source.buildinfo
Files:
 995f8544c8fff3d1bac97dd1f8ab78a3 2153 admin optional 
crun_0.17+dfsg-1+deb11u2.dsc
 3eb260655e6e687bff16f0ed8dc7cc88 16236 admin optional 
crun_0.17+dfsg-1+deb11u2.debian.tar.xz
 8ff612e30f091feff3e574fb4dadaf1d 7391 admin optional 
crun_0.17+dfsg-1+deb11u2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEqVksUhy5BAd9ZZgAnQteWx7sjw4FAmVQhNwACgkQnQteWx7s
jw4h3A//QCi7o1Bys48D26uk99aUqoeTHT5/eCCe6Z+1OWyGbSRJP/acSsZLgRZT
r5nN/c+9Cyhmd71G421TMb6SVywEw2u9AN25piAY8tCUDXF3FLnMB2KiBYNOLS5t
0uhVGfDwMf+eoRnBEiZwGM/maHcfNY9BoShye87BD/PN7sC91xfeXO1IwW+UdF8p
hdndEprmHUFm84nli/14pI3b2gk8OYwmom9wHLIYiXUq+N58A/64JFobfMaB6aWK
mUC7vSq0FgINzfyIVE+ookjJ9rvVJPuQIgBUeZ+kV4tF02awoUL5C/r8kjbi49OG
EcnCUew5V/CmmzlnTazjPknnsmT8WP75l0cwJwHm0pgOub7FnsCUBw6+xsR5y4YL
FDpTgMtHxjkT6y4ZTxiEP6aGOA3EbI3d47zeW90x2blzFDvHQz4dvtk3SfV0Xjbz
2z1TnziQZX0AcQ/v4ll8Js6mePOKgdrLpe9rikky+v5AMc7N+hM82N3cTETn5KBp
q5gfnOjQT7ThliyiGkCCU1qmhPVfKDRoXXhdCv/RAqxetWqiZDktXuY37Dfsdsjb
NwL4hELrr5GV9rd7Y2GlnVIiKIbU8UyUgVj1MBy+hCjUHxPZkqqPbegFZYr99TLH
dP7tJt/D//CpmR8dJF5f9DTVyxYdP9UnKPnvwRAdSDqg2DCoM2c=
=rG72
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to