Your message dated Sat, 31 Aug 2024 12:13:11 +0000 with message-id <e1skmyd-00gq6f...@coccia.debian.org> and subject line Close 1076137 has caused the Debian Bug report #1076137, regarding bullseye-pu: package containerd/1.4.13~ds1-1~deb11u4 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.) -- 1076137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: release.debian.org Severity: normal Tags: bullseye User: release.debian....@packages.debian.org Usertags: pu X-Debbugs-Cc: ritesh-ku...@siemens.com (Please provide enough information to help the release team to judge the request efficiently. E.g. by filling in the sections below.) [ Reason ] (Explain what the reason for the (old-)stable update is. I.e. what is the bug, when was it introduced, is this a regression with respect to the previous (old-)stable.) When we start a container using Docker usually through a systemd service or via the command line and user does not handle the termination of the running container, the containerd-shim process hangs during poweroff/reboot sequence. ==> systemd-shutdown[1]: Waiting for process: 2011 (containerd-shim) Although this behavior seems normal from my perspective because it forces the user to take action and make a graceful shutdown. The right way to stop the containers gracefully was via the systemd service by using ExecStop directive primarily(sends the SIGTERM signal from systemd service to docker which in turn sends to containerd that handles the container shutdown), TimeoutStopSec and KillSignal=SIGTERM. [ Impact ] (What is the impact for the user if the update isn't approved?) The containerd-shim process hangs during poweroff/reboot sequence. systemd-shutdown[1]: Waiting for process: 2011 (containerd-shim) [ Tests ] (What automated or manual tests cover the affected code?) Steps to reproduce: 1. the easiest to reproduce is from the command line # docker pull --platform linux/arm64 alpine 2. # docker run -d --name container-test alpine tail -f /dev/null 3. # docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 57e1c1658c20 alpine "tail -f /dev/null" 8 seconds ago Up 5 seconds container-test 4. # systemctl reboot For more details Check here:- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073148 [ Risks ] (Discussion of the risks involved. E.g. code is trivial or complex, alternatives available.) I don't think this could be major risk as this we need to backport from upstream containerd repo. Upstream discussion: https://github.com/containerd/containerd/issues/5502 Upstream patch: https://github.com/containerd/containerd/pull/5828 [ Checklist ] [*] *all* changes are documented in the d/changelog [*] I reviewed all changes and I approve them [ ] attach debdiff against the package in (old)stable [ ] the issue is verified as fixed in unstable [ Changes ] (Explain *all* the changes) Here I have pushed the changes please have a look and decide whether we need to add or not. https://salsa.debian.org/go-team/packages/containerd/-/merge_requests/3 [ Other info ] (Anything else the release team should know.) Please have a look for the bug created by Siemens. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073148
--- End Message ---
--- Begin Message ---We regret that your request could not be reviewed in time for the final point release of bullseye (11.11).
--- End Message ---
