Devuan bug report logs - #596
podman: Podman shows systemd journal error messages

Full log

Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):

Received: (at submit) by bugs.devuan.org; 23 Jul 2021 19:00:01 +0000
Return-Path: <void@rittich.net>
Delivered-To: devuanbugs@dyne.org
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Fri, 23 Jul 2021 19:00:01 +0000 (UTC)
Received: from [127.0.1.1] (v2202105148788153697.goodsrv.de [94.16.112.139])
	by vm6.ganeti.dyne.org (Postfix) with ESMTP id 5DF75F60D64
	for <submit@bugs.devuan.org>; Fri, 23 Jul 2021 20:55:19 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Hannah Rittich <void@rittich.net>
To: Devuan Bug Tracking System <submit@bugs.devuan.org>
Subject: podman: Podman shows systemd journal error messages
Message-ID: <162707371784.4203.15006124007437811971.reportbug@devuan-vm>
Date: Fri, 23 Jul 2021 22:55:17 +0200
X-Spam-Status: No, score=1.2 required=5.0 tests=HELO_MISC_IP,KHOP_DYNAMIC,
	SPF_FAIL autolearn=disabled version=3.4.2
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

Package: podman
Version: 3.0.1+dfsg1-3+b1
Severity: minor
X-Debbugs-Cc: void@rittich.net

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:

    [engine]
    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

Send a report that this bug log contains spam.