[Containerfile]: how to prevent archive skipping socket warning from spamming the console?

[GrabbenD]

Question

This is a follow-up from my previous inquiry about keeping console warning/error messages to the minimum to allow the operator to easily spot any potential issues: #19603

When the container contains socket files (e.g. generated by gnupg) it spams the console with multiple warnings

WARN[0008] archive: skipping %q since it is a socket

Reference: containers/storage#1115

Reproduce

Dockerfile:

FROM archlinux:base AS rootfs

# Generate a GPG secret key for signing and populate the keyring
RUN pacman-key --init && \
    pacman-key --populate

Result

$ podman build
[1/2] STEP 1/7: FROM archlinux:base AS rootfs
[1/2] STEP 2/7: RUN pacman-key --init &&     pacman-key --populate
==> Generating pacman master key. This may take some time.
gpg: Generating pacman keyring master key...
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/E807897C95AC85121E12EDE3855EA1BE0786A03E.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   2  signed:   5  trust: 0-, 0q, 0n, 0m, 0f, 2u
gpg: depth: 1  valid:   5  signed:  95  trust: 0-, 0q, 0n, 5m, 0f, 0u
gpg: depth: 2  valid:  73  signed:  27  trust: 73-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2023-10-27
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signed 5 keys.
==> Importing owner trust values...
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   2  signed:   5  trust: 0-, 0q, 0n, 0m, 0f, 2u
gpg: depth: 1  valid:   5  signed:  95  trust: 0-, 0q, 0n, 5m, 0f, 0u
gpg: depth: 2  valid:  73  signed:  27  trust: 73-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2023-10-27
WARN[0008] archive: skipping "/var/lib/containers/storage/overlay/f9411622836b11ff3534b51792d0a241db08185f2a1f485f32bfb7209fc810c6/merged/etc/pacman.d/gnupg/S.gpg-agent" since it is a socket
WARN[0008] archive: skipping "/var/lib/containers/storage/overlay/f9411622836b11ff3534b51792d0a241db08185f2a1f485f32bfb7209fc810c6/merged/etc/pacman.d/gnupg/S.gpg-agent.browser" since it is a socket
WARN[0008] archive: skipping "/var/lib/containers/storage/overlay/f9411622836b11ff3534b51792d0a241db08185f2a1f485f32bfb7209fc810c6/merged/etc/pacman.d/gnupg/S.gpg-agent.extra" since it is a socket
WARN[0008] archive: skipping "/var/lib/containers/storage/overlay/f9411622836b11ff3534b51792d0a241db08185f2a1f485f32bfb7209fc810c6/merged/etc/pacman.d/gnupg/S.gpg-agent.ssh" since it is a socket

What I've tried

I've tried to fix this warning with .containerignore file to no avail:

S.gpg-agent
*S.gpg-agent
**/S.gpg-agent
*/S.gpg-agent

However, it's possible to silent this warning by using volumes but I found this approach to be undesirable for building a multi-stage container for a OSTree image:

$ podman build -o rootfs
$ ls rootfs/etc/pacman.d/gnupg/
crls.d  gpg-agent.conf  gpg.conf  openpgp-revocs.d  private-keys-v1.d  pubring.gpg  pubring.gpg~  secring.gpg  tofu.db  trustdb.gpg

versus:

$ podman build -v $(pwd)/gnupg:/etc/pacman.d/gnupg -o rootfs
$ ls rootfs/etc/pacman.d/gnupg/
gpg-agent.conf  gpg.conf  openpgp-revocs.d  private-keys-v1.d  pubring.gpg  secring.gpg  tofu.db  trustdb.gpg

---

Is there any proper way to silent this warning?

[rhatdan]

podman --log-level=error build ...

[rhatdan]

Actually I do not know if this Warning is coming from us, I believe it is coming from pacman
So my idea probably would do nothing.

[GrabbenD]

This warning was introduced here: containers/storage#1116
Here's the relevant line in main: pkg/archive/archive.go#L480

Anything which uses sockets like gnupg in Pacman will generate this error

[rhatdan]

Open a PR to drop the message to Infor, not Warn and it should disappear.

[pohlt]

Opened a PR as suggested: containers/storage#1776