On 08.03.2022 18:20, Manuel Wagesreither wrote:
> Hi all,
>
> Am Do, 3. Mär 2022, um 19:02, schrieb Lennart Poettering:
>> On Mi, 02.03.22 17:50, Lennart Poettering (lenn...@poettering.net) wrote:
>>
>>> That said, we could certainly show both the comm field and the PID of
>>> the offending
Hi all,
Am Do, 3. Mär 2022, um 19:02, schrieb Lennart Poettering:
> On Mi, 02.03.22 17:50, Lennart Poettering (lenn...@poettering.net) wrote:
>
>> That said, we could certainly show both the comm field and the PID of
>> the offending processes. I am prepping a patch for that.
>
> See:
On Fr, 04.03.22 08:20, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> >> Something seems to be off with containerd's integration into systemd but
> >> I'm not sure what.
> >
> > Docker traditionally has not followed any of our documented ways to
>
> You are implying that "our
On 04/03/2022 07:20, Ulrich Windl wrote:
Docker traditionally has not followed any of our documented ways to
You are implying that "our documented ways" is a definitive standard?
cgroups is a THIRD PARTY to both Docker and systemd. If Docker doesn't
document what they're doing, how is
>>> Lennart Poettering schrieb am 02.03.2022 um 17:22
in
Nachricht :
> On Mi, 02.03.22 13:02, Arian van Putten (arian.vanput...@gmail.com) wrote:
>
>> I've seen this a lot with docker/containerd. It seems as if for some
reason
>> systemd doesn't wait for their cgroups to cleaned up on shutdown.
On Mi, 02.03.22 17:50, Lennart Poettering (lenn...@poettering.net) wrote:
> That said, we could certainly show both the comm field and the PID of
> the offending processes. I am prepping a patch for that.
See: https://github.com/systemd/systemd/pull/22655
Lennart
--
Lennart Poettering, Berlin
On 3/2/22 11:50, Lennart Poettering wrote:
On Mi, 02.03.22 12:29, Manuel Wagesreither (man...@fastmail.fm) wrote:
Hi all,
My embedded system is shutting down rather slow, and I'd like to find out the
responsible processes.
[ 7668.571133] systemd-shutdown[1]: Waiting for process: dockerd,
On Mi, 02.03.22 12:29, Manuel Wagesreither (man...@fastmail.fm) wrote:
> Hi all,
>
> My embedded system is shutting down rather slow, and I'd like to find out the
> responsible processes.
>
> [ 7668.571133] systemd-shutdown[1]: Waiting for process: dockerd, python3
> [ 7674.670684]
On Mi, 02.03.22 13:02, Arian van Putten (arian.vanput...@gmail.com) wrote:
> I've seen this a lot with docker/containerd. It seems as if for some reason
> systemd doesn't wait for their cgroups to cleaned up on shutdown. It's
> very easy to reproduce. Start a docker container and then power off
I've seen this a lot with docker/containerd. It seems as if for some reason
systemd doesn't wait for their cgroups to cleaned up on shutdown. It's
very easy to reproduce. Start a docker container and then power off the
machine. Since the move to cgroups V2 containerd should be using systemd to
Hi all,
My embedded system is shutting down rather slow, and I'd like to find out the
responsible processes.
[ 7668.571133] systemd-shutdown[1]: Waiting for process: dockerd, python3
[ 7674.670684] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
Is there a way for
11 matches
Mail list logo
