:: [devuan-dev] bug#596: marked as don…
Top Page
Delete this message
Reply to this message
Author: Devuan bug Tracking System
To: dak
Subject: [devuan-dev] bug#596: marked as done (podman: Podman shows systemd journal error messages)
Your message dated Wed, 28 Jul 2021 15:19:17 +0000
with message-id <1627485557.221148.4032.nullmailer@???>
and subject line #596: fixed in src:debian-config-override version 2.1
has caused the Devuan bug report #596,
regarding podman: Podman shows systemd journal error messages
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 owner@???

596: https://bugs.devuan.org/cgi/bugreport.cgi?bug=596
Devuan Bug Tracking System
Contact owner@??? with problems
Package: podman
Version: 3.0.1+dfsg1-3+b1
Severity: minor
X-Debbugs-Cc: void@???

Using podman on chimaera results in many spurious error messages that result
from podman trying to write to the systemd journal.

These error messages can be avoided by creating the file
`/etc/containers/containers.conf` containing:

    cgroup_manager = "cgroupfs"
    events_logger = "file"

To make the default configuration more user friendly, this file could be
included in the podman package. (The first line is needed in order to be
able to use podman at all, see [Bug 595].)

Steps to reproduce:

1. Install podman.
2. Execute the following commands

        $ podman pull docker.io/dyne/devuan:beowulf

        $ podman run --rm -ti dyne/devuan:beowulf
        ERRO[0000] unable to write pod event: "write unixgram @0001d->/run/systemd/journal/socket: sendmsg: no such file or directory"
        ERRO[0000] unable to write pod event: "write unixgram @0001d->/run/systemd/journal/socket: sendmsg: no such file or directory"
        ERRO[0000] unable to write pod event: "write unixgram @0001d->/run/systemd/journal/socket: sendmsg: no such file or directory"
        ERRO[0000] unable to write pod event: "write unixgram @0001d->/run/systemd/journal/socket: sendmsg: no such file or directory"

3. Create the file `/etc/containers/containers.conf` as described above.
4. Repeat 2.

[Bug 595]: https://bugs.devuan.org/cgi/bugreport.cgi?bug=595

-- System Information:
Distributor ID:    Devuan
Description:    Devuan GNU/Linux 4 (chimaera)
Release:    4
Codename:    n/a
Architecture: x86_64

Kernel: Linux 5.10.0-8-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages podman depends on:
ii  conmon                           2.0.25+ds1-1
ii  containernetworking-plugins      0.9.0-1+b6
ii  crun                             0.17+dfsg-1
ii  golang-github-containers-common  0.33.4+ds1-1
ii  init-system-helpers              1.60+devuan1
ii  iptables                         1.8.7-1
ii  libc6                            2.31-12
ii  libdevmapper1.02.1               2:1.02.175-2.1
ii  libgpgme11                       1.14.0-1+b2
ii  libseccomp2                      2.5.1-1

Versions of packages podman recommends:
ii  buildah                                           1.19.6+dfsg1-1+b5
ii  catatonit                                         0.1.5-2
ii  fuse-overlayfs                                    1.4.0-1
ii  golang-github-containernetworking-plugin-dnsname  1.1.1+ds1-4+b7
ii  slirp4netns                                       1.0.1-2
ii  uidmap                                            1:4.8.1-1

Versions of packages podman suggests:
pn  containers-storage  <none>
pn  docker-compose      <none>

-- no debconf information

Version: 2.1

Source package debian-config-override (2.1) added to Devuan suite unstable.

This closes bug report 596.


DAK managing the Devuan archive

Hash: SHA512

Format: 1.8
Date: Wed, 28 Jul 2021 14:02:56 +0100
Source: debian-config-override
Architecture: source
Version: 2.1
Distribution: unstable
Urgency: medium
Maintainer: Mark Hindley <mark@???>
Changed-By: Mark Hindley <mark@???>
Closes: 595 596
debian-config-override (2.1) unstable; urgency=medium
* Add debian-podman-config-override (Closes: #595, #596).
969da60f121aa4bdb6f10b1a6bbbc86f67c14a2a 1514 debian-config-override_2.1.dsc
d81ea2156a9d1005e1e9438890f8bd615c16c345 2220 debian-config-override_2.1.tar.xz
3cad827f959634f4ba8a3efb80f99e707680cd1a 5245 debian-config-override_2.1_source.buildinfo
6c820034946475f949d9991c341998f1e282d786eff25ba5edc91ad8cf7d0ecd 1514 debian-config-override_2.1.dsc
93dd35a1af1b60c7c8e41820b855f960f80eb9192121beb68a93ccb8157846e0 2220 debian-config-override_2.1.tar.xz
d76e4f19f5ea43f9c4989ff2da0bd682fe355487db1bcc86591e79ae66203187 5245 debian-config-override_2.1_source.buildinfo
f2ea2db986f6543cb991a5c3e7c0d331 1514 misc optional debian-config-override_2.1.dsc
c0d594f530ddbdd297988bbd30a5c22b 2220 misc optional debian-config-override_2.1.tar.xz
f3595c61e9b77f3eea1c5dd556ddb316 5245 misc optional debian-config-override_2.1_source.buildinfo